June 2007 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (ANN-544) @SqlDeleteAll wrt to Collections

by Thomas Kubicek (JIRA)

@SqlDeleteAll wrt to Collections -------------------------------- Key: ANN-544 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-544 Project: Hibernate Annotations Type: Bug Components: binder Versions: 3.2.1 Environment: 3.2.1GA - MSSQL ( but irrelivant ) Reporter: Thomas Kubicek Hibernate Annotations for @SqlDeleteAll when applied to Collections CollectionBinder is not assigning the sql statement to the "setCustomSQLDeleteAll" but rather the "setCustomSQLDelete" CollectionBinder.java line 361-370. this prevents the execution of col.clear() method on the collection where all elements are removed. -- 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

18 years, 9 months

3
3
0 / 0

[Hibernate-JIRA] Created: (HHH-2598) Mapping a collection of entities from two different classes with the same collection name results in duplicate backref property exception if collection keys are not null

by Guido Scalise (JIRA)

Mapping a collection of entities from two different classes with the same collection name results in duplicate backref property exception if collection keys are not null ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: HHH-2598 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2598 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.3, 3.2.2, 3.2.1 Environment: Proven on Hibernate 3.2.2 and 3.2.3, PostgreSQL 8.2.3, WindowsXP, Java 1.5 Reporter: Guido Scalise Attachments: backref.patch, Hibernate-bug.zip Mapping a child entity collection from two different parent entities results in duplicate backref property exception when configuring the session factory if the collection keys are marked not null and the collection names are the same in both parents. Log is: (cfg.Environment 509 ) Hibernate 3.2.3 (cfg.Environment 542 ) hibernate.properties not found (cfg.Environment 676 ) Bytecode provider name : cglib (cfg.Environment 593 ) using JDK 1.4 java.sql.Timestamp handling (cfg.Configuration 1426) configuring from resource: /hibernate.cfg.xml (cfg.Configuration 1403) Configuration resource: /hibernate.cfg.xml (cfg.Configuration 553 ) Reading mappings from resource : com/bbsw/tests/ParentA.hbm.xml (cfg.HbmBinder 300 ) Mapping class: com.bbsw.tests.ParentA -> PARENT_A (cfg.Configuration 553 ) Reading mappings from resource : com/bbsw/tests/ParentB.hbm.xml (cfg.HbmBinder 300 ) Mapping class: com.bbsw.tests.ParentB -> PARENT_B (cfg.Configuration 553 ) Reading mappings from resource : com/bbsw/tests/Child.hbm.xml (cfg.HbmBinder 300 ) Mapping class: com.bbsw.tests.Child -> CHILD (cfg.Configuration 1541) Configured SessionFactory: null (cfg.HbmBinder 2375) Mapping collection: com.bbsw.tests.ParentA.children -> CHILD (cfg.HbmBinder 2375) Mapping collection: com.bbsw.tests.ParentB.children -> CHILD Exception in thread "main" org.hibernate.MappingException: Duplicate property mapping of _childrenBackref found in com.bbsw.tests.Child at org.hibernate.mapping.PersistentClass.checkPropertyDuplication(PersistentClass.java:459) at org.hibernate.mapping.PersistentClass.validate(PersistentClass.java:449) at org.hibernate.mapping.RootClass.validate(RootClass.java:192) at org.hibernate.cfg.Configuration.validate(Configuration.java:1102) at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1287) at HBTest.main(HBTest.java:17) The problem seems to be originated during the second Collection binding pass in org.hibernate.cfg.HbmBinder, as the Backrefs and IndexBackrefs names are created like this: (Excerpts from HbmBinder.java r10921 2006-12-05 14:39:12Z steve.ebersole(a)jboss.com, contained in the Hibernate 3.2.3.ga source) line 2242: IndexBackref ib = new IndexBackref(); line 2243: ib.setName( '_' + node.attributeValue( "name" ) + "IndexBackref" ); and line 2478: Backref prop = new Backref(); line 2479: prop.setName( '_' + node.attributeValue( "name" ) + "Backref" ); in both cases the node name value is the collection name. So for every collection that points to a child, Hibernate creates a backref property without considering the posibility of more than one entity declaring the same collection name. I've patched the code to add the collection owner's entity name to the property name, and it worked without problems. I'm attaching: * ParentA, ParentB and Child classes * Mappings for ParentA, ParentB and Child * hbm.xml file * Main test case. (HBTest.java) * Proposed patch in unified diff format. -- 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

18 years, 10 months

4
5
0 / 0

[Hibernate-JIRA] Created: (HHH-2433) Use of an id together with a natural-id results in an ArraIndexOutOfBoundsException

by Danny Bols (JIRA)

Use of an id together with a natural-id results in an ArraIndexOutOfBoundsException ------------------------------------------------------------------------------------ Key: HHH-2433 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2433 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.1 Environment: MySql, Cocoon, WindowsXp Reporter: Danny Bols Attachments: hb-issue.txt Use of a natural-id in combination with a generated id results in an ArrayOutOfBoundsException. The table in the database has 2 unique keys, a natural-id and an internal id (UUID). A record is loaded in a separate transaction and send to a user form. When the user hits the save button the changes are committed in a new transaction. If this transaction doesn't contain a new load of the record the commit will result in an ArrayIndexOutOfBoundsException. If we leave out the natural-id definition in the config file we don't get an exception. See attachement for details. -- Danny -- 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

18 years, 10 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2593) Keyword UNION is prefixed with "this_." in filter conditions

by Frederic Leitenberger (JIRA)

Keyword UNION is prefixed with "this_." in filter conditions ------------------------------------------------------------ Key: HHH-2593 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2593 Project: Hibernate3 Issue Type: Bug Components: query-hql, query-sql Affects Versions: 3.2.1 Environment: Oracle 10g: org.hibernate.dialect.OracleDialect Suse Linux Hibernate: 3.2.1.ga Hibernate Annotations: 3.2.1.GA Reporter: Frederic Leitenberger Priority: Trivial I need to use a UNION-Subquery in a Filter condition unless HHH-298 is solved. But anyway, when using the keyword "union" in the Filter condition it is prefixed with "this_.". For instance, this ... @Filter(name = "resellerFilter", condition = "(select cu.resellerId from Customer cu, GeoNumber gn where (cu.id = gn.customerId and gn.id = this_.geoNumberId) UNION select cu.resellerId from Customer cu where cu.detemeTemplateId = this_.id) in (null, :resellerIds)") ... produces this ... select ... from DeTeMe this_ where ( select cu.resellerId from Customer cu, GeoNumber gn where ( cu.id = gn.customerId and gn.id = this_.geoNumberId ) this_.UNION select cu.resellerId from Customer cu where cu.detemeTemplateId = this_.id ) in ( null, ? ) and this_.id = ? -- 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

18 years, 10 months

2
5
0 / 0

[Hibernate-JIRA] Created: (HHH-2667) 'illegal attempt to dereference collection' when using auto-join

by Martin Kouba (JIRA)

'illegal attempt to dereference collection' when using auto-join ---------------------------------------------------------------- Key: HHH-2667 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2667 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.2.4.sp1, 3.2.4, 3.2.3 Environment: I have found that behaviour in version 3.2.4.sp1 and 3.2.3 (I didn't test 3.2.4 pre sp1) Database: ORACLE 10g Reporter: Martin Kouba After upgrading to the latest Hibernate version I got this error. I try to use a statement like this from cat c where c.mate.id = 13 the expected resulting SQL should be something like SELECT * FROM CAT C WHERE C.MATE_ID = 13 which is much more performant than making a join from cat c join c.mate m where m.id = 13 which would result in something like that SELECT * FROM CAT C INNER JOIN MATE M ON C.MATE_ID = M.ID WHERE M.ID = 13 This works as expected in 3.1.3, 3.2.0 and 3.2.2 It doesn't work with version 3.2.3 and with 3.2.4.sp1. -- 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

18 years, 10 months

8
25
0 / 0

[Hibernate-JIRA] Created: (HHH-2475) Split lib directory

by Christian Bauer (JIRA)

Split lib directory ------------------- Key: HHH-2475 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2475 Project: Hibernate3 Type: Improvement Components: build Reporter: Christian Bauer I've read again that Hibernate "requires 40 JARs" and that the fantastic Oracle reference implementation does not. This nonsense can only be stopped by splitting the lib/ subdirectory of our distribution into /lib/required, lib/optional, and lib/buildtime. Consider for 3.3. -- 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

18 years, 10 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2682) support for H2 in DialectFactory

by Dan Allen (JIRA)

support for H2 in DialectFactory -------------------------------- Key: HHH-2682 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2682 Project: Hibernate3 Issue Type: Improvement Components: core Affects Versions: 3.2.4.sp1 Environment: Hibernate 3 EJB3 JPA Reporter: Dan Allen For some reason, the H2 database is not included in the dialect factory map, even though there is a Hibernate dialect available for this database. Please add the following to org.hibernate.dialect.DialectFactory MAPPERS.put( "H2", new VersionInsensitiveMapper( "org.hibernate.dialect.H2Dialect" ) ); -- 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

18 years, 10 months

3
6
0 / 0

[Hibernate-JIRA] Created: (HHH-2070) Improvement for DialectFactory

by Martin Renner (JIRA)

Improvement for DialectFactory ------------------------------ Key: HHH-2070 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2070 Project: Hibernate3 Type: Patch Components: core Versions: 3.2.0.cr4 Reporter: Martin Renner Attachments: DialectFactory.patch I would like to have more entries for autodetecting DB2 dialects. According to HHH-1467 I created a patch. At the moment, DialectFactory knows just "DB2/NT". We are currently using DB2Dialect for "DB2/6000" and "DB2/LINUX", but we would like to have Hibernate autodetect these dialects. So the patch simply adds two new lines to DialectFactory. It would be really helpful for us, if this patch would make it into 3.1.x and 3.2.x. The patch works for 3.1.3 and 3.2.0cr4. -- 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

18 years, 10 months

3
4
0 / 0

[Hibernate-JIRA] Created: (HHH-2297) invalid id type error message doesn't report which entity

by Kelly Campbell (JIRA)

invalid id type error message doesn't report which entity --------------------------------------------------------- Key: HHH-2297 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2297 Project: Hibernate3 Type: Patch Components: metamodel Versions: 3.2.0.ga Reporter: Kelly Campbell Priority: Minor Attachments: hibernate-id-type.patch The error message given here makes it very hard to determine what entity has the problem. Simple patch is attached. java.lang.UnsupportedOperationException: not a valid id type at org.hibernate.type.CharacterType.getDefaultValue(CharacterType.java:20) at org.hibernate.engine.UnsavedValueFactory.getUnsavedIdentifierValue(UnsavedValueFactory.java:48) at org.hibernate.tuple.PropertyFactory.buildIdentifierProperty(PropertyFactory.java:44) at org.hibernate.tuple.EntityMetamodel.(EntityMetamodel.java:114) at org.hibernate.persister.entity.AbstractEntityPersister.(AbstractEntityPersister.java:418) at org.hibernate.persister.entity.SingleTableEntityPersister.(SingleTableEntityPersister.java:108) at org.hibernate.persister.PersisterFactory.createClassPersister(PersisterFactory.java:55) at org.hibernate.impl.SessionFactoryImpl.(SessionFactoryImpl.java:223) at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1213) at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:631) at org.hibernate.ejb.Ejb3Configuration.createEntityManagerFactory(Ejb3Configuration.java:760) at org.hibernate.ejb.Ejb3Configuration.createFactory(Ejb3Configuration.java:151) at org.hibernate.ejb.Ejb3Configuration.createEntityManagerFactory(Ejb3Configuration.java:205) -- 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

18 years, 10 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2261) Setting hibernate.hbm2ddl.auto=validate causes problems on mySQL with numeric fields

by Christian Sprajc (JIRA)

Setting hibernate.hbm2ddl.auto=validate causes problems on mySQL with numeric fields ------------------------------------------------------------------------------------ Key: HHH-2261 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2261 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.1 Reporter: Christian Sprajc Hello, We got a Problem when using the following setup: 1) JBoss 4.0.4A with Hibernate 3.2.0 / mySQl 4.x AND 5.x 2) Set hibernate.hbm2ddl.auto=validate 3) Using a usertype which uses the SQL type: Types.NUMERIC When deploying our application I got the following error: 12:43:21,985 INFO [TableMetadata] columns: [paymenttype, amount, oid, remarks, currency, ae_date] 12:43:21,985 WARN [ServiceController] Problem starting service persistence.units:jar=com.riege.pogo_0.1.4.jar,unitName=PogoEntityManager org.hibernate.HibernateException: Wrong column type: amount, expected: numeric(19,2) at org.hibernate.mapping.Table.validateColumns(Table.java:251) at org.hibernate.cfg.Configuration.validateSchema(Configuration.java:1002) The Problem is: 1) When hibernate creates (e.g. hibernate.hbm2ddl.auto=update) through the columns in the mySQL database it creates it as "numeric(x,y)" field. 2) mySQL always converts "numeric(x,y)" to "decimal(x,y)". The metadata returns "decimal(x,y)" 3) When deploying with "hibernate.hbm2ddl.auto=validate" to error above is thrown. The problem is that hibernate expects a "numeric(x,y)" type but mysql returns a "decimal(x,y)" A workaround I'm now using is a fixed mySQL dialect which correctly handles Types.DECIMAL / "decimal(x,y)": public class FixedMySQLDialect extends org.hibernate.dialect.MySQLDialect { public FixedMySQLDialect() { super(); registerColumnType(Types.NUMERIC, "decimal(19, $l)"); registerColumnType(Types.DECIMAL, "decimal(19, $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

18 years, 10 months

2
3
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues June 2007