January 2007 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-2382) DefaultLoadEventListener#onLoad throws exception when DelayedPostInsertIdentifier is set as an entity id

by Eelco Hillenius (JIRA)

DefaultLoadEventListener#onLoad throws exception when DelayedPostInsertIdentifier is set as an entity id -------------------------------------------------------------------------------------------------------- Key: HHH-2382 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2382 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.1, 3.2.2, 3.2.0.ga Reporter: Eelco Hillenius DefaultLoadEventListener#onLoad has this code: if ( idClass != null && ! idClass.isInstance( event.getEntityId() ) ) { throw new TypeMismatchException( "Provided id of the wrong type. Expected: " + idClass + ", got " + event.getEntityId().getClass()); } However, EntityIdentityInsertAction has this in it's constructor: delayedEntityKey = isDelayed ? generateDelayedEntityKey() : null; and method: private synchronized EntityKey generateDelayedEntityKey() { if ( !isDelayed ) { throw new AssertionFailure( "cannot request delayed entity-key for non-delayed post-insert-id generation" ); } return new EntityKey( new DelayedPostInsertIdentifier(), getPersister(), getSession().getEntityMode() ); } In case an insert is tried outside of an existing transaction users may run into this problem (like I did). I don't know what the best fix is. The easiest fix would be: Index: /Users/eelcohillenius/Documents/workspace/hibernate3/src/org/hibernate/event/def/DefaultLoadEventListener.java =================================================================== --- /Users/eelcohillenius/Documents/workspace/hibernate3/src/org/hibernate/event/def/DefaultLoadEventListener.java (revision 11098) +++ /Users/eelcohillenius/Documents/workspace/hibernate3/src/org/hibernate/event/def/DefaultLoadEventListener.java (working copy) @@ -5,6 +5,7 @@ import org.apache.commons.logging.Log; import org.apache.commons.logging.LogFactory; +import org.hibernate.EntityMode; import org.hibernate.HibernateException; import org.hibernate.LockMode; import org.hibernate.NonUniqueObjectException; @@ -10,7 +11,7 @@ import org.hibernate.NonUniqueObjectException; import org.hibernate.PersistentObjectException; import org.hibernate.TypeMismatchException; -import org.hibernate.EntityMode; +import org.hibernate.action.DelayedPostInsertIdentifier; import org.hibernate.cache.CacheConcurrencyStrategy; import org.hibernate.cache.CacheKey; import org.hibernate.cache.entry.CacheEntry; @@ -82,7 +83,7 @@ } else { Class idClass = persister.getIdentifierType().getReturnedClass(); - if ( idClass != null && ! idClass.isInstance( event.getEntityId() ) ) { + if ( idClass != null && ! (idClass.isInstance( event.getEntityId() ) || event.getEntityId() instanceof DelayedPostInsertIdentifier )) { throw new TypeMismatchException( "Provided id of the wrong type. Expected: " + idClass + ", got " + event.getEntityId().getClass() ); but that would look like a quick hack to me. -- 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

16 years, 7 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-2183) org.hibernate.LazyInitializationException: failed to lazily initialize a collection while using lazy set with key as property-ref in the mapping

by Artur Jonak (JIRA)

org.hibernate.LazyInitializationException: failed to lazily initialize a collection while using lazy set with key as property-ref in the mapping ------------------------------------------------------------------------------------------------------------------------------------------------ Key: HHH-2183 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2183 Project: Hibernate3 Type: Bug Components: core Versions: 3.1.3 Environment: Oracle 9i Reporter: Artur Jonak Priority: Blocker Attachments: hibernate-testcase.zip I have an entity which can have multiple titles located in a separate table. I mapped this as a set where key attribute references other property of the entity: <set name="titles" table="TTitle" cascade="none" lazy="true" inverse="true" mutable="false"> <key column="ID" property-ref="parentId"/>  <element type="string" column="title"/> </set> when I try to display this set I get an exception: org.hibernate.LazyInitializationException: failed to lazily initialize a collection of role: test.lazysetinit.Record.titles, no session or session was closed at org.hibernate.collection.AbstractPersistentCollection.throwLazyInitializationException(AbstractPersistentCollection.java:358) at org.hibernate.collection.AbstractPersistentCollection.throwLazyInitializationExceptionIfNotConnected(AbstractPersistentCollection.java:350) at org.hibernate.collection.AbstractPersistentCollection.initialize(AbstractPersistentCollection.java:343) at org.hibernate.collection.AbstractPersistentCollection.read(AbstractPersistentCollection.java:86) ... The entire mapping is as follows: <class name="Record" table="TRecord" mutable="false"> <id name="id" type="long"> <column name="ID" sql-type="number" length="12" not-null="true" unique="true"/> </id> <set name="titles" table="TTitle" cascade="none" lazy="true" inverse="true" mutable="false"> <key column="ID" property-ref="parentId"/>  <element type="string" column="title"/> </set> <join table="TRecordInfo" inverse="true" fetch="join" optional="false"> <key column="ID"/> <property name="parentId" not-null="false" /> <property name="status" /> </join> </class> Attached the test case: test.lazysetinit.LazySetInitTest. DB schema is located in test/conf/lazysetinit/schema.sql Regards, Artur -- 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

16 years, 8 months

5
5
0 / 0

[Hibernate-JIRA] Created: (HB-1570) CLONE -dropIndex doesn't cound on Dialect

by Ohad Bruker (JIRA)

CLONE -dropIndex doesn't cound on Dialect ----------------------------------------- Key: HB-1570 URL: http://opensource.atlassian.com/projects/hibernate/browse/HB-1570 Project: Hibernate2 Type: Bug Components: core Versions: 2.1.6 Environment: Hibernate 2.1.6, MySql 4.?? Reporter: Ohad Bruker In class net.sf.hibernate.mapping.Index method sqlDropString(Dialect dialect) doesn't count on dialect, and always makes name of index qualified: return "drop index " + StringHelper.qualify( table.getQualifiedName(dialect), name); This will fail at least in case of MySql DB, because it doesn't understand {tablename}.{indexname} constructions, but {indexname} only. I propose next edition: return "drop index " + (dialect.qualifyIndexName() ? StringHelper.qualify( table.getQualifiedName(dialect), name) : name); Is it suitable? -- 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

16 years, 8 months

4
7
0 / 0

[Hibernate-JIRA] Created: (HBX-852) start hql/criteria editing based on selected project

by Max Rydahl Andersen (JIRA)

start hql/criteria editing based on selected project ---------------------------------------------------- Key: HBX-852 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-852 Project: Hibernate Tools Type: Improvement Components: eclipse Versions: 3.2beta9 Reporter: Max Rydahl Andersen now that projects know which console configuration they are associated too we can start hql/criteria editing directly on a consoleconfig when a resource in a project is selected. probably should have an action set (in toolbar or menu) together with adding it to a context sensitive right menu. -- 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

16 years, 8 months

2
8
0 / 0

[Hibernate-JIRA] Created: (HHH-2118) hibernate cant find dialect class and drivers cause of blanks in hibernate.property file

by Daniel Lärm (JIRA)

hibernate cant find dialect class and drivers cause of blanks in hibernate.property file ----------------------------------------------------------------------------------------- Key: HHH-2118 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2118 Project: Hibernate3 Type: Bug Components: core, build Versions: 3.2.0.cr4 Environment: Red Hat Enterprise Linux 4 Windows XP SP2 Ingres2006 Reporter: Daniel Lärm The ingres section in the hibernate.property file consists of 4 lines, where at the end of each line is an blank, that is not neccesary and causes errors when building hibernate and running the certification tests. The first line generates an error, that he cant find the ingres dialect class, the second, that he cant find the jdbc driver and so on. After removing these blanks, there are none of these errors and it is working fine. In the svn trunk of hibernate 3 there are also blanks there. Perhaps these problems are also with other database sections in the property file, but i didnt check them. Daniel -- 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

16 years, 8 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2155) mysql dialect should not generate automatically index for foreign key

by Anthony Patricio (JIRA)

mysql dialect should not generate automatically index for foreign key --------------------------------------------------------------------- Key: HHH-2155 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2155 Project: Hibernate3 Type: Improvement Components: core Environment: MySQL Reporter: Anthony Patricio Priority: Minor Attachments: patch-mysqlDialect.txt MySQLDialect.getAddForeignKeyConstraintString(String, String[], String, String[], boolean) method is generating also index which is not wanted. Here is the modified method: public String getAddForeignKeyConstraintString( String constraintName, String[] foreignKey, String referencedTable, String[] primaryKey, boolean referencesPrimaryKey ) { String cols = StringHelper.join(", ", foreignKey); return new StringBuffer(30) //.append(" add index ") //.append(constraintName) //.append(" (") //.append(cols) //.append("), add constraint ") .append(" add constraint ") .append(constraintName) .append(" foreign key (") .append(cols) .append(") references ") .append(referencedTable) .append(" (") .append( StringHelper.join(", ", primaryKey) ) .append(')') .toString(); } -- 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

16 years, 8 months

2
1
0 / 0

[Hibernate-JIRA] Created: (EJB-217) Multiple @OneToMany(fetch=FetchType.EAGER) relationships not supported

by Michał Borowiecki (JIRA)

Multiple @OneToMany(fetch=FetchType.EAGER) relationships not supported ----------------------------------------------------------------------- Key: EJB-217 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-217 Project: Hibernate Entity Manager Type: Bug Versions: 3.2.0.cr1 Environment: JBoss4.0.4.GA Reporter: Michał Borowiecki Having more than one relationship on en entity annotated with @OneToMany(fetch=FetchType.EAGER) causes exception when deploying the ejb3 module: org.hibernate.HibernateException: cannot simultaneously fetch multiple bags. This bug is thoroughly explained here: http://www.jroller.com/page/eyallupu?entry=hibernate_exception_simultaneo... and depends on HHH-1718 "Have multiple bag fetches revert to subselect fetching for all but one of the bags" The temporary solution in HHH-1413 - disallowing multiple bag fetches is unsuitable to ejb3 environment, because the spec does not disallow it. -- 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

16 years, 9 months

3
3
0 / 0

[Hibernate-JIRA] Created: (HHH-2073) many-to-one join fetch with optional parent causing stray query to fire

by Adam Hardy (JIRA)

many-to-one join fetch with optional parent causing stray query to fire ----------------------------------------------------------------------- Key: HHH-2073 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2073 Project: Hibernate3 Type: Bug Reporter: Adam Hardy Priority: Minor Attachments: bugtest.zip I have a call centre application which uses a mature database and is therefore pushing Hibernate to accomplish the mappings I need. The issue here is extra queries that Hibernate is firing where I set up the mapping to do a join in one hit. I am fetching child objects which may or may not have a parent. The child's foreign key points to a non-primary key on the parent. This is not reflected by a foreign key constraint in the database (hence it allows child to have no parent). If the child object has the foreign key 0 instead of null, which is the protocol in this database, then the parent which doesn't exist is not (& cannot) be instantiated, no problem, but then after processing the resultset, Hibernate fires off another query to fetch the parent that it could not find data for in the first query. This is obviously unnecessary in this context and degrades the performance on large searches on this child. I have classified it as minor since I suspect there may be work-arounds but I have not researched that yet. I didn't know whether I could put the mapping XML in the query, so I have attached a simplistic testcase example that demonstrates the problem. The following forum messages are relevant and the latter contains the mappings, which is easier than extracting them out of the testcase zip: http://forum.hibernate.org/viewtopic.php?t=960522 http://forum.hibernate.org/viewtopic.php?t=964211 -- 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

16 years, 9 months

2
1
0 / 0

[Hibernate-JIRA] Created: (ANN-442) Support @GenericGenerators

by Emmanuel Bernard (JIRA)

Support @GenericGenerators -------------------------- Key: ANN-442 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-442 Project: Hibernate Annotations Type: New Feature Components: binder Reporter: Emmanuel Bernard Priority: Minor To support more than one generic generator in package-info.java -- 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

16 years, 10 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-2384) Patch for using case-expression("case ... when ... end") in aggregate functions

by Florian Rock (JIRA)

Patch for using case-expression("case ... when ... end") in aggregate functions ------------------------------------------------------------------------------- Key: HHH-2384 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2384 Project: Hibernate3 Type: Patch Components: query-hql Versions: 3.2.2 Reporter: Florian Rock Priority: Minor Attachments: aggrcasehql.patch using a case-expression in aggregate functions causes a QuerySyntaxException.. ie.: "count(case when fubar > 0 then 1 else null end)" i changed some things in the grammar to solve this, patch is attached. -- 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

16 years, 11 months

4
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues January 2007