[Hibernate-JIRA] Resolved: (HHH-1141) informix Dialect bug
by Diego Pires Plentz (JIRA)
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1141?page=c... ]
Diego Pires Plentz resolved HHH-1141.
-------------------------------------
Assignee: Diego Pires Plentz
Resolution: Duplicate
> informix Dialect bug
> --------------------
>
> Key: HHH-1141
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1141
> Project: Hibernate3
> Issue Type: Bug
> Components: metamodel
> Affects Versions: 3.1 rc 1
> Environment: Informix Dynamic Server Version 10.0, Informix JDBC
> driver version 3.0
> Reporter: ls
> Assignee: Diego Pires Plentz
>
> informix Database no support double data type
> public InformixDialect() {
> super();
> registerColumnType(Types.BIGINT, "int8");
> registerColumnType(Types.BINARY, "byte");
> registerColumnType(Types.BIT, "smallint"); // Informix doesn't have a
> // bit type
> registerColumnType(Types.CHAR, "char($l)");
> registerColumnType(Types.DATE, "date");
> registerColumnType(Types.DECIMAL, "decimal");
> // registerColumnType(Types.DOUBLE, "double"); ----- error
> -----> registerColumnType(Types.DOUBLE, "float") or registerColumnType(Types.DOUBLE, "double precision") --- right ;
>
> registerColumnType(Types.FLOAT, "float");
> registerColumnType(Types.INTEGER, "integer");
> registerColumnType(Types.LONGVARBINARY, "blob"); // or BYTE
> registerColumnType(Types.LONGVARCHAR, "clob"); // or TEXT?
> registerColumnType(Types.NUMERIC, "decimal"); // or MONEY
> registerColumnType(Types.REAL, "smallfloat");
> registerColumnType(Types.SMALLINT, "smallint");
> registerColumnType(Types.TIMESTAMP, "datetime year to fraction(5)");
> registerColumnType(Types.TIME, "datetime hour to second");
> registerColumnType(Types.TINYINT, "smallint");
> registerColumnType(Types.VARBINARY, "byte");
> registerColumnType(Types.VARCHAR, "varchar($l)");
> }
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 5 months
[Hibernate-JIRA] Updated: (HHH-1616) org.hibernate.tuple.ElementWrapper has 6 Java scoping errors which break updating a lazy-loaded DOM4J Element
by Christian Bauer (JIRA)
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1616?page=c... ]
Christian Bauer updated HHH-1616:
---------------------------------
Comment: was deleted
> org.hibernate.tuple.ElementWrapper has 6 Java scoping errors which break updating a lazy-loaded DOM4J Element
> -------------------------------------------------------------------------------------------------------------
>
> Key: HHH-1616
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1616
> Project: Hibernate3
> Issue Type: Bug
> Components: core
> Affects Versions: 3.2.0 cr1
> Environment: Any
> Reporter: John Spackman
> Attachments: ElementWrapper.java
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> The class has a member variable called "element" which is the DOM4J element that is being wrapped; 6 of the methods in ElementWrapper (from the Element interface) have parameters also called "element" and the scoping is not corrected to use the wrapped "element".
> EG, calling the method "add" to add a new child element will make the child a child of itself and *not* connect it to the wrapped element. See snippet below
> public class ElementWrapper implements Element, Serializable {
> private Element element;
> private Element parent;
> // ...snip...
> public void add(Element element) {
> // BUG: Should be this.element.add(..)
> element.add( element );
> }
> // ...snip...
> }
> This methods affected are:
> getPath
> getUniquePath
> asXPathResult
> appendAttributes
> add(Element element)
> remove(Element element)
> Attached is a fixed version, with comments by my changes.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 5 months
[Hibernate-JIRA] Commented: (HHH-1616) org.hibernate.tuple.ElementWrapper has 6 Java scoping errors which break updating a lazy-loaded DOM4J Element
by Jay Schrock (JIRA)
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1616?page=c... ]
Jay Schrock commented on HHH-1616:
----------------------------------
Why is this issue still unassigned, Created March 2006 ?
> org.hibernate.tuple.ElementWrapper has 6 Java scoping errors which break updating a lazy-loaded DOM4J Element
> -------------------------------------------------------------------------------------------------------------
>
> Key: HHH-1616
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1616
> Project: Hibernate3
> Issue Type: Bug
> Components: core
> Affects Versions: 3.2.0 cr1
> Environment: Any
> Reporter: John Spackman
> Attachments: ElementWrapper.java
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> The class has a member variable called "element" which is the DOM4J element that is being wrapped; 6 of the methods in ElementWrapper (from the Element interface) have parameters also called "element" and the scoping is not corrected to use the wrapped "element".
> EG, calling the method "add" to add a new child element will make the child a child of itself and *not* connect it to the wrapped element. See snippet below
> public class ElementWrapper implements Element, Serializable {
> private Element element;
> private Element parent;
> // ...snip...
> public void add(Element element) {
> // BUG: Should be this.element.add(..)
> element.add( element );
> }
> // ...snip...
> }
> This methods affected are:
> getPath
> getUniquePath
> asXPathResult
> appendAttributes
> add(Element element)
> remove(Element element)
> Attached is a fixed version, with comments by my changes.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 5 months
[Hibernate-JIRA] Created: (HHH-2783) The Element Wrapper Java module has a number of methods, mainly the add method is incorrect.
by Jay Schrock (JIRA)
The Element Wrapper Java module has a number of methods, mainly the add method is incorrect.
--------------------------------------------------------------------------------------------
Key: HHH-2783
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2783
Project: Hibernate3
Issue Type: Bug
Affects Versions: 3.2.4
Environment: 3.2 Oracle
Reporter: Jay Schrock
The WrapperElement class has an instance attribute called "element". This class also has a number of methods of which their signature has a parameter also called element. In a number of these methods the name conflicts with the instance attribute and incorrect behavior. In particular the add method has a parameter called element. In the implementation of the add method, there is a call element.add( element). This is incorrect and produces bad XML results and also causes recursive elements in the XML... What should happen is that the key "this" should be used to indicate that the instance attributes "element" should be used. I believe the implementation should be this.element.add( element). Also one needs to look at a number of other methods that also may have this problem....
thanks, Jay Schrock
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 5 months
[Hibernate-JIRA] Commented: (HHH-1396) Table.validateColumns fails on valid column
by Diego Pires Plentz (JIRA)
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1396?page=c... ]
Diego Pires Plentz commented on HHH-1396:
-----------------------------------------
Max, the first part of the problem I already solved.
> Table.validateColumns fails on valid column
> -------------------------------------------
>
> Key: HHH-1396
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1396
> Project: Hibernate3
> Issue Type: Bug
> Components: metamodel
> Affects Versions: 3.1.1
> Reporter: Christopher G. Stach II
> Assignee: Diego Pires Plentz
> Priority: Minor
>
> This may be an Annotations bug (3.1beta8), bug the exception happens in Core.
> This column used to pass when I used this:
> @Column(columnDefinition = "INT UNSIGNED NOT NULL DEFAULT 0", nullable = false)
> I have since changed it to
> @Column(columnDefinition = "INT UNSIGNED DEFAULT 0", nullable = false)
> because "nullable = false" adds the "not null".
> I am guessing that the nullable isn't being used in the validateColumns. I have not yet investigated, but the stack trace is below.
> org.hibernate.tool.hbm2ddl.TableMetadata.<init> table found: xxx.yyy
> org.hibernate.tool.hbm2ddl.TableMetadata.<init> columns: [foo_id, ipaddress, actiontype, timestamp, id]
> com.caucho.server.webapp.Application.start org.hibernate.HibernateException: Wrong column type: ipAddress, expected: INT UNSIGNED DEFAULT 0
> at org.hibernate.mapping.Table.validateColumns(Table.java:219)
> at org.hibernate.cfg.Configuration.validateSchema(Configuration.java:964)
> at org.hibernate.tool.hbm2ddl.SchemaValidator.validate(SchemaValidator.java:116)
> at org.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:296)
> at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1164)
> [...]
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 5 months
[Hibernate-JIRA] Created: (HHH-2790) Problems during hibernate initialization with JBoss treecache / jgroups
by Andreas Røsdal (JIRA)
Problems during hibernate initialization with JBoss treecache / jgroups
-----------------------------------------------------------------------
Key: HHH-2790
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2790
Project: Hibernate3
Issue Type: Bug
Reporter: Andreas Røsdal
I'm having some problems with a website which uses Hibernate with JBoss
TreeCache. Several servers with the following configuration:
Resin application server, with Hibernate 3, with JBoss TreeCache.
The problem occurs during startup of the Resin application server,
occurs during initialization of hibernate, and the result is that when
this occurs no .jsp pages are served from Resin which uses Hibernate.
Most of the threads in the Resin application server are waiting for a
thread in the jgroups classes. However, this function never finishes,
causing all new tcpConnection threads to wait, until the application
server crashes.
Here is the full stack dump from java while the problem occurs:
http://www.pvv.org/~andrearo/java-stack-dump.txt
Here is the relevant thread which causes the problem:
"tcpConnection-6802-19" daemon prio=1 tid=0x0825f300 nid=0x1354 in Object.wait() [0xaef01000..0xaef01878]
at java.lang.Object.wait(Native Method)
- waiting on <0x51ed2f78> (a org.jgroups.util.Promise)
at java.lang.Object.wait(Object.java:429)
at org.jgroups.util.Promise.doWait(Promise.java:100)
at org.jgroups.util.Promise._getResultWithTimeout(Promise.java:52)
at org.jgroups.util.Promise.getResultWithTimeout(Promise.java:28)
- locked <0x51ed2f78> (a org.jgroups.util.Promise)
at org.jgroups.util.Promise.getResult(Promise.java:77)
at org.jgroups.JChannel.connect(JChannel.java:353)
Any advice about what could be the cause of these problems? How should I
go about further investigating this? I have briefly looked at
the getResultWithTimeout() method in the Promise class from jgroups.
Any help would be appreciated!
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 5 months
[Hibernate-JIRA] Commented: (HHH-1396) Table.validateColumns fails on valid column
by Max Rydahl Andersen (JIRA)
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1396?page=c... ]
Max Rydahl Andersen commented on HHH-1396:
------------------------------------------
this is a well known issue with schemavalidator - it does not handle compatible types, but with different string names correctly.
search for validator issues and you will see ,)
> Table.validateColumns fails on valid column
> -------------------------------------------
>
> Key: HHH-1396
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1396
> Project: Hibernate3
> Issue Type: Bug
> Components: metamodel
> Affects Versions: 3.1.1
> Reporter: Christopher G. Stach II
> Assignee: Diego Pires Plentz
> Priority: Minor
>
> This may be an Annotations bug (3.1beta8), bug the exception happens in Core.
> This column used to pass when I used this:
> @Column(columnDefinition = "INT UNSIGNED NOT NULL DEFAULT 0", nullable = false)
> I have since changed it to
> @Column(columnDefinition = "INT UNSIGNED DEFAULT 0", nullable = false)
> because "nullable = false" adds the "not null".
> I am guessing that the nullable isn't being used in the validateColumns. I have not yet investigated, but the stack trace is below.
> org.hibernate.tool.hbm2ddl.TableMetadata.<init> table found: xxx.yyy
> org.hibernate.tool.hbm2ddl.TableMetadata.<init> columns: [foo_id, ipaddress, actiontype, timestamp, id]
> com.caucho.server.webapp.Application.start org.hibernate.HibernateException: Wrong column type: ipAddress, expected: INT UNSIGNED DEFAULT 0
> at org.hibernate.mapping.Table.validateColumns(Table.java:219)
> at org.hibernate.cfg.Configuration.validateSchema(Configuration.java:964)
> at org.hibernate.tool.hbm2ddl.SchemaValidator.validate(SchemaValidator.java:116)
> at org.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:296)
> at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1164)
> [...]
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 5 months
[Hibernate-JIRA] Assigned: (HHH-1396) Table.validateColumns fails on valid column
by Diego Pires Plentz (JIRA)
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1396?page=c... ]
Diego Pires Plentz reassigned HHH-1396:
---------------------------------------
Assignee: Diego Pires Plentz
> Table.validateColumns fails on valid column
> -------------------------------------------
>
> Key: HHH-1396
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1396
> Project: Hibernate3
> Issue Type: Bug
> Components: metamodel
> Affects Versions: 3.1.1
> Reporter: Christopher G. Stach II
> Assignee: Diego Pires Plentz
> Priority: Minor
>
> This may be an Annotations bug (3.1beta8), bug the exception happens in Core.
> This column used to pass when I used this:
> @Column(columnDefinition = "INT UNSIGNED NOT NULL DEFAULT 0", nullable = false)
> I have since changed it to
> @Column(columnDefinition = "INT UNSIGNED DEFAULT 0", nullable = false)
> because "nullable = false" adds the "not null".
> I am guessing that the nullable isn't being used in the validateColumns. I have not yet investigated, but the stack trace is below.
> org.hibernate.tool.hbm2ddl.TableMetadata.<init> table found: xxx.yyy
> org.hibernate.tool.hbm2ddl.TableMetadata.<init> columns: [foo_id, ipaddress, actiontype, timestamp, id]
> com.caucho.server.webapp.Application.start org.hibernate.HibernateException: Wrong column type: ipAddress, expected: INT UNSIGNED DEFAULT 0
> at org.hibernate.mapping.Table.validateColumns(Table.java:219)
> at org.hibernate.cfg.Configuration.validateSchema(Configuration.java:964)
> at org.hibernate.tool.hbm2ddl.SchemaValidator.validate(SchemaValidator.java:116)
> at org.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:296)
> at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1164)
> [...]
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 5 months
[Hibernate-JIRA] Assigned: (HHH-1396) Table.validateColumns fails on valid column
by Diego Pires Plentz (JIRA)
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1396?page=c... ]
Diego Pires Plentz reassigned HHH-1396:
---------------------------------------
Assignee: Diego Pires Plentz
> Table.validateColumns fails on valid column
> -------------------------------------------
>
> Key: HHH-1396
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1396
> Project: Hibernate3
> Issue Type: Bug
> Components: metamodel
> Affects Versions: 3.1.1
> Reporter: Christopher G. Stach II
> Assignee: Diego Pires Plentz
> Priority: Minor
>
> This may be an Annotations bug (3.1beta8), bug the exception happens in Core.
> This column used to pass when I used this:
> @Column(columnDefinition = "INT UNSIGNED NOT NULL DEFAULT 0", nullable = false)
> I have since changed it to
> @Column(columnDefinition = "INT UNSIGNED DEFAULT 0", nullable = false)
> because "nullable = false" adds the "not null".
> I am guessing that the nullable isn't being used in the validateColumns. I have not yet investigated, but the stack trace is below.
> org.hibernate.tool.hbm2ddl.TableMetadata.<init> table found: xxx.yyy
> org.hibernate.tool.hbm2ddl.TableMetadata.<init> columns: [foo_id, ipaddress, actiontype, timestamp, id]
> com.caucho.server.webapp.Application.start org.hibernate.HibernateException: Wrong column type: ipAddress, expected: INT UNSIGNED DEFAULT 0
> at org.hibernate.mapping.Table.validateColumns(Table.java:219)
> at org.hibernate.cfg.Configuration.validateSchema(Configuration.java:964)
> at org.hibernate.tool.hbm2ddl.SchemaValidator.validate(SchemaValidator.java:116)
> at org.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:296)
> at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1164)
> [...]
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 5 months