February 2007 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (EJB-266) lazy initialization of one-to-many bidirectional relationships through cascade.persist

by sara forghani (JIRA)

lazy initialization of one-to-many bidirectional relationships through cascade.persist -------------------------------------------------------------------------------------- Key: EJB-266 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-266 Project: Hibernate Entity Manager Type: Bug Components: EntityManager Versions: 3.2.1 Environment: hibernate 3.2.2, hibernate-entitymanager 3.2.1.ga Reporter: sara forghani Priority: Critical hibernate initializes lazy objects traversed by the persist operation; for example, in this case (the project is attached): class A has bidirectional one-to-many relationship to classes B1, B2, B3, B4 (b1List, b2List, b3List, b4List) B1 has bidirectional one-to-many relationship to C1 (c1List) B2 has bidirectional one-to-many relationship to C2 (c2List) if we try persisting C2, it will also initialize B1, C1, B4 ... and other existing C2's (you may find a more complete description of the issue at http://forum.hibernate.org/viewtopic.php?p=2340004#2340004) -- 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, 10 months

3
8
0 / 0

[Hibernate-JIRA] Created: (HHH-2119) reloading a detached object with a collection fails

by Gregory Kotsaftis (JIRA)

reloading a detached object with a collection fails --------------------------------------------------- Key: HHH-2119 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2119 Project: Hibernate3 Type: Bug Versions: 3.1.3 Environment: Hibernate 3.1.3 firebird 1.5.3.4870 with Jaybird-2.1.0 java 1.5.0_07 Reporter: Gregory Kotsaftis Hi, 1) I have a simple object <O> with a collection loaded and use <version> for both (no second level cache) 2) The object <O> is associated with session A, via <O> = load(CLASS, <ID>) 3) The session <A> is later closed because e.g. an exception occurs 4) Another session is opened later on, session B 5) If load(<O>, <ID>) is called an NonUniqueObjectException is thrown (a different object with the same identifier value was already associated with the session) 6) If instead I use the session.refresh(<O>) no exception is thrown, the object is reloaded ok. It seems this issue might be related with: http://opensource.atlassian.com/projects/hibernate/browse/HHH-511 but i cannot be sure. Part of the stacktrace: org.hibernate.NonUniqueObjectException: a different object with the same identifier value was already associated with the session: [gr.metadata.orthomed.db.Patient#23] at org.hibernate.event.def.DefaultLoadEventListener.load(DefaultLoadEventListener.java:132) at org.hibernate.event.def.DefaultLoadEventListener.returnNarrowedProxy(DefaultLoadEventListener.java:202) at org.hibernate.event.def.DefaultLoadEventListener.proxyOrLoad(DefaultLoadEventListener.java:169) at org.hibernate.event.def.DefaultLoadEventListener.onLoad(DefaultLoadEventListener.java:87) at org.hibernate.impl.SessionImpl.fireLoad(SessionImpl.java:862) at org.hibernate.impl.SessionImpl.load(SessionImpl.java:770) at gr.metadata.lib.hibernate.HibernateHelper.reloadObject(HibernateHelper.java:230) -- 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, 10 months

2
5
0 / 0

[Hibernate-JIRA] Created: (ANN-484) Do not filter classes on queries when we know that Directory <-> Entity is a one to one relationship

by Emmanuel Bernard (JIRA)

Do not filter classes on queries when we know that Directory <-> Entity is a one to one relationship ---------------------------------------------------------------------------------------------------- Key: ANN-484 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-484 Project: Hibernate Annotations Type: Improvement Components: lucene Reporter: Emmanuel Bernard Priority: Minor -- 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, 10 months

1
2
0 / 0

[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

17 years, 11 months

2
3
0 / 0

[Hibernate-JIRA] Created: (EJB-270) Support eclipse bundleresource protocol

by Emmanuel Bernard (JIRA)

Support eclipse bundleresource protocol --------------------------------------- Key: EJB-270 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-270 Project: Hibernate Entity Manager Type: New Feature Components: EntityManager Reporter: Emmanuel Bernard Assigned to: Emmanuel Bernard As soon as someone provides me a simple eclipse project reproducing EJB-242, I am going a have a look at this bug to properly support bundleresource. I would appreciate the users to put pressure on Eclispe to fix their bug, their URL should be readable as stream and not raise NPEs -- 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, 11 months

3
8
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

17 years, 11 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

17 years, 11 months

4
7
0 / 0

[Hibernate-JIRA] Created: (HHH-2453) Inserting BIT to PostgreSQL table

by Imran M Yousuf (JIRA)

Inserting BIT to PostgreSQL table --------------------------------- Key: HHH-2453 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2453 Project: Hibernate3 Type: Bug Components: query-sql Environment: Not sure about the hibernate version but will add it soon, downloaded last June. PostrgreSQL 8.2.3 on RedHat Fedora Core 1. Spring Framework. Reporter: Imran M Yousuf Attachments: CallUser.hbm.xml, hibernate_pgsql.properties I created a Table which has a column active as Boolean in the entity and the HBM file specifies the type as boolean. When I use this configuration with MySQL it works fine, but when I use it with PostgreSQL I get an javax.sql.BatchUpdateException. so later I changed the HBM file 'active' column type to 'yes_no' and than it works fine. So I confirmed that the problem is due to the BIT(1) column. So I next tried to manually insert into the column and it PgSQL tells that 1 needs to be casted. Please let me know if I can help in other ways, I will be most grateful to help. Thank you, Imran -- 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, 11 months

2
1
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

17 years, 11 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

17 years, 11 months

2
1
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 February 2007