June 2009 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-2498) Lazy Inverse Map Bug?

by CannonBall (JIRA)

Lazy Inverse Map Bug? --------------------- Key: HHH-2498 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2498 Project: Hibernate3 Type: Bug Versions: 3.2.1, 3.2.2 Environment: Hibernate 3.2.2, Java5, MySQL 5 (InnoDB) Reporter: CannonBall Priority: Minor Mapping documents: <hibernate-mapping> <class name="scratchpad.hibernate.A"> <id name="id"> <generator class="assigned"/> </id> <map name="bs" cascade="all-delete-orphan" inverse="true"> <key column="aId"/> <map-key type="long" column="cId"/> <one-to-many class="scratchpad.hibernate.B"/> </map> </class> <class name="scratchpad.hibernate.B"> <id name="id"> <generator class="assigned"/> </id> <many-to-one name="a" class="scratchpad.hibernate.A" column="aId"/> <many-to-one name="c" class="scratchpad.hibernate.C" column="cId" not-null="true"/> </class> <class name="scratchpad.hibernate.C"> <id name="id"> <generator class="assigned"/> </id> </class> </hibernate-mapping> Code between sessionFactory.openSession() and session.close(): long aId = 1l; long bId = 2l; long cId = 3l; SessionFactory factory = new Configuration().configure() .buildSessionFactory(); try { Session s = factory.openSession(); try { Transaction tx = s.beginTransaction(); try { C c = new C(cId); s.save(c); A a = new A(aId); B b = new B(bId); b.setC(c); b.setA(a); a.getBs().put(cId, b); s.save(a); tx.commit(); } catch (Exception e) { try { tx.rollback(); } catch (Exception e2) { // do nothing } throw e; } } finally { s.close(); } s = factory.openSession(); try { Transaction tx = s.beginTransaction(); try { A a = (A) s.load(A.class, aId); a.getBs().remove(cId); tx.commit(); } catch (Exception e) { try { tx.rollback(); } catch (Exception e2) { // do nothing } throw e; } } finally { s.close(); } } finally { factory.close(); } Name and version of the database you are using: MySQL 5.0.33 The generated SQL (show_sql=true): Hibernate: select b_.id, b_.aId as aId1_, b_.cId as cId1_ from B b_ where b_.id=? Hibernate: insert into C (id) values (?) Hibernate: insert into A (id) values (?) Hibernate: insert into B (aId, cId, id) values (?, ?, ?) Hibernate: select a0_.id as id0_0_ from A a0_ where a0_.id=? Hibernate: select bs0_.aId as aId1_, bs0_.id as id1_, bs0_.cId as cId1_, bs0_.id as id1_0_, bs0_.aId as aId1_0_, bs0_.cId as cId1_0_ from B bs0_ where bs0_.aId=? I've been having a confusing problem shown above, whereby A has a Map of Bs indexed using the id from an association with C. This Map is inversely mapped for A and with 'Cascade Delete Orphan'. In the second opened session above, where B is removed from A's Map and thus orphaned, B will not be deleted. I have observed B is only deleted if I either set 'lazy="false"' for A's Map or make an interaction with A's Map in the code (before B's removal) like 'a.getBs().get(cId)'. I suspect the lazy intializer is not initializing correctly in the above scenario. The above scenario does not happen if A's Map is not inversely mapped but B's many-to-one with A is. Can somebody shed some light on whether this is me using Hibernate incorrectly or is a bug? -- 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

4
6
0 / 0

[Hibernate-JIRA] Created: (HHH-3504) Hibernate 3.3.1GA issue when using CGLIB

by Montagnon Cyril (JIRA)

Hibernate 3.3.1GA issue when using CGLIB ---------------------------------------- Key: HHH-3504 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3504 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.3.1 Environment: Database : hsqldb/Sybase Reporter: Montagnon Cyril When forcing hibernate to use CGLIB (by the way javassist is still slower than CGLib), I get the following exception (at the end of the post) It seems that the repackaging of the CGLIB project (hibernate-cglib-repack) doesn't behave as expected : Shouldn't it look up for the org.hibernate.repackage.cglib.proxy.Callback class instead of the net.sf.cglib.proxy.Callback class. java.lang.NoClassDefFoundError: net.sf.cglib.proxy.Callback at org.hibernate.repackage.cglib.proxy.Enhancer.class$(Enhancer.java:68) at org.hibernate.repackage.cglib.proxy.Enhancer.getCallbacksSetter(Enhancer.java:627) at org.hibernate.repackage.cglib.proxy.Enhancer.setCallbacksHelper(Enhancer.java:615) at org.hibernate.repackage.cglib.proxy.Enhancer.setThreadCallbacks(Enhancer.java:609) at org.hibernate.repackage.cglib.proxy.Enhancer.registerCallbacks(Enhancer.java:578) at org.hibernate.proxy.pojo.cglib.CGLIBLazyInitializer.getProxyInstance(CGLIBLazyInitializer.java:133) at org.hibernate.proxy.pojo.cglib.CGLIBLazyInitializer.getProxy(CGLIBLazyInitializer.java:116) at org.hibernate.proxy.pojo.cglib.CGLIBProxyFactory.getProxy(CGLIBProxyFactory.java:72) at org.hibernate.tuple.entity.AbstractEntityTuplizer.createProxy(AbstractEntityTuplizer.java:402) at org.hibernate.persister.entity.AbstractEntityPersister.createProxy(AbstractEntityPersister.java:3483) at org.hibernate.event.def.DefaultLoadEventListener.createProxyIfNecessary(DefaultLoadEventListener.java:298) at org.hibernate.event.def.DefaultLoadEventListener.proxyOrLoad(DefaultLoadEventListener.java:219) at org.hibernate.event.def.DefaultLoadEventListener.onLoad(DefaultLoadEventListener.java:126) at org.hibernate.impl.SessionImpl.fireLoad(SessionImpl.java:905) at org.hibernate.impl.SessionImpl.load(SessionImpl.java:822) at org.hibernate.impl.SessionImpl.load(SessionImpl.java:815) at org.springframework.orm.hibernate3.HibernateTemplate$3.doInHibernate(HibernateTemplate.java:566) at org.springframework.orm.hibernate3.HibernateTemplate.doExecute(HibernateTemplate.java:419) at org.springframework.orm.hibernate3.HibernateTemplate.executeWithNativeSession(HibernateTemplate.java:374) at org.springframework.orm.hibernate3.HibernateTemplate.load(HibernateTemplate.java:560) at org.springframework.orm.hibernate3.HibernateTemplate.load(HibernateTemplate.java:554) at north.stardust2.core.test.unit.dao.listed.IndexCompositionDaoTest.findIndexCompositionByListedIndexAt(IndexCompositionDaoTest.java:36) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.junit.internal.runners.TestMethod.invoke(TestMethod.java:59) at org.junit.internal.runners.MethodRoadie.runTestMethod(MethodRoadie.java:98) at org.junit.internal.runners.MethodRoadie$2.run(MethodRoadie.java:79) at org.junit.internal.runners.MethodRoadie.runBeforesThenTestThenAfters(MethodRoadie.java:87) at org.junit.internal.runners.MethodRoadie.runTest(MethodRoadie.java:77) at org.junit.internal.runners.MethodRoadie.run(MethodRoadie.java:42) at org.junit.internal.runners.JUnit4ClassRunner.invokeTestMethod(JUnit4ClassRunner.java:88) at org.junit.internal.runners.JUnit4ClassRunner.runMethods(JUnit4ClassRunner.java:51) at org.junit.internal.runners.JUnit4ClassRunner$1.run(JUnit4ClassRunner.java:44) at org.junit.internal.runners.ClassRoadie.runUnprotected(ClassRoadie.java:27) at org.junit.internal.runners.ClassRoadie.runProtected(ClassRoadie.java:37) at org.junit.internal.runners.JUnit4ClassRunner.run(JUnit4ClassRunner.java:42) at org.junit.internal.runners.CompositeRunner.runChildren(CompositeRunner.java:33) at org.junit.runners.Suite.access$000(Suite.java:26) at org.junit.runners.Suite$1.run(Suite.java:93) at org.junit.internal.runners.ClassRoadie.runUnprotected(ClassRoadie.java:27) at org.junit.internal.runners.ClassRoadie.runProtected(ClassRoadie.java:37) at org.junit.runners.Suite.run(Suite.java:91) at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:45) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196) -- 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

16
36
0 / 0

[Hibernate-JIRA] Created: (ANN-782) InterceptFieldCallback is being mapped again since its package changed in Hibernate core 3.3.1

by Alex Gitelman (JIRA)

InterceptFieldCallback is being mapped again since its package changed in Hibernate core 3.3.1 ---------------------------------------------------------------------------------------------- Key: ANN-782 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-782 Project: Hibernate Annotations Issue Type: Bug Components: binder Affects Versions: 3.4.0.GA Reporter: Alex Gitelman Hibernate-core generate fields of type 'org.hibernate.repackage.cglib.transform.impl.InterceptFieldCallback' instead of net.sf package, therefore fix from ANN-133 can't work >From AnnotationBinder: {code} private static boolean mustBeSkipped(XProperty property, ExtendedMappings mappings) { //TODO make those hardcoded tests more portable (through the bytecode provider?) return property.isAnnotationPresent( Transient.class ) || "net.sf.cglib.transform.impl.InterceptFieldCallback".equals( property.getType().getName() ) || "org.hibernate.bytecode.javassist.FieldHandler".equals( property.getType().getName() ); } {code} -- 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

3
3
0 / 0

[Hibernate-JIRA] Created: (ANN-840) Primary key fields needs to be non-null on some databases

by Juraci Paixao Krohling (JIRA)

Primary key fields needs to be non-null on some databases --------------------------------------------------------- Key: ANN-840 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-840 Project: Hibernate Annotations Issue Type: Bug Affects Versions: 3.4.0.GA, 3.3.1.GA Environment: Sybase ASE 15 Reporter: Juraci Paixao Krohling Assignee: Juraci Paixao Krohling Fix For: 3.3.2, 3.4.1 As described in JBPAPP-1071, some databases requires primary key columns be non-null. -- 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-3523) org.hibernate.id.enhanced.SequenceStyleGenerator causes org.hibernate.MappingException with SAPDB and DB2Dialect

by Damir Malenicic (JIRA)

org.hibernate.id.enhanced.SequenceStyleGenerator causes org.hibernate.MappingException with SAPDB and DB2Dialect ---------------------------------------------------------------------------------------------------------------- Key: HHH-3523 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3523 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.1 Environment: Hibernate 3.3.1.GA Generation of DDL scripts for DB2Dialect and SAPDBDialect Reporter: Damir Malenicic Attachments: db2-sapdb-bug.zip While generating DDL scripts for mapping files that declare id <generator class="org.hibernate.id.enhanced.SequenceStyleGenerator"> the following exception is thrown: org.hibernate.MappingException: Dialect does not support pooled sequences at org.hibernate.dialect.Dialect.getCreateSequenceString(Dialect.java:701) at org.hibernate.dialect.Dialect.getCreateSequenceStrings(Dialect.java:659) at org.hibernate.id.enhanced.SequenceStructure.sqlCreateStrings(SequenceStructure.java:139) at org.hibernate.id.enhanced.SequenceStyleGenerator.sqlCreateStrings(SequenceStyleGenerator.java:328) at org.hibernate.cfg.Configuration.generateSchemaCreationScript(Configuration.java:945) at org.hibernate.tool.hbm2ddl.SchemaExport.<init>(SchemaExport.java:129) at org.hibernate.tool.hbm2ddl.SchemaExport.<init>(SchemaExport.java:91) I suspect the cause is in org.hibernate.dialect.Dialect#getCreateSequenceString(String sequenceName, int initialValue, int incrementSize) if ( supportsPooledSequences() ) { return getCreateSequenceString( sequenceName ) + " start with " + initialValue + " increment by " + incrementSize; } throw new MappingException( "Dialect does not support pooled sequences" ); This call requires not just that dialect supports sequences but that dialect supports pooled sequences. But the algorithm that tries to determine whether the table should be used to emulate the sequence lets the dialects that supports sequences but not pooled sequences to slip through. It looks like the DB2 and SAPDB dialects fail in this category because of: org.hibernate.id.enhanced.SequenceStyleGenerator#configure(Type type, Properties params, Dialect dialect) ... if ( dialect.supportsSequences() && !forceTableUse ) { if ( OptimizerFactory.POOL.equals( optimizationStrategy ) && !dialect.supportsPooledSequences() ) { forceTableUse = true; log.info( "Forcing table use for sequence-style generator due to pooled optimizer selection where db does not support pooled sequences" ); } } To workaround the problem I have created my generator that overrides SequenceStyleGenerator#configure, somethng like: public void configure(Type type, Properties params, Dialect dialect) throws MappingException { if (dialect.supportsSequences() && !dialect.supportsPooledSequences()) { params.setProperty(FORCE_TBL_PARAM, "true"); } super.configure(type, params, dialect); Attached is a zip file with a small maven project with unit-test that replicates the problem. It generates DDL for different databases: Hipersonic, Derby, Oracle, MySql, PostgreSQL, MSSQL, DB2, and SAPDB. The data-model contains 2 tables Person and Event in many-to-many relation. -- 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
1
0 / 0

[Hibernate-JIRA] Commented: (HHH-1724) Critieria needs to be aligned with new aggreation type rules

by Max Rydahl Andersen (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1724?page=c... ] Max Rydahl Andersen commented on HHH-1724: ------------------------------------------ Yes it sounds perfectly reasonable - should have been done from the beginning but for some reason the function types on Dialect where only used by HQL, not by Criteria - if that had been the case the problem wouldn't be here. > Critieria needs to be aligned with new aggreation type rules > ------------------------------------------------------------ > > Key: HHH-1724 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1724 > Project: Hibernate Core > Issue Type: Bug > Components: core > Reporter: Max Rydahl Andersen > Assignee: Steve Ebersole > Priority: Blocker > Fix For: 3.5 > > > Criteria does not ask the dialect about the type + it does not always seem to know what the underlying field type is..... > created as blocker to make sure we either document or fix 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, 10 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-3937) Inheritance + join table problem for table per subclass mapping

by vivek meghanathan (JIRA)

Inheritance + join table problem for table per subclass mapping --------------------------------------------------------------- Key: HHH-3937 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3937 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.2.6 Environment: 3.3.6.GA, mysql5.0, windows/linux Reporter: vivek meghanathan Attachments: myorder.hbm.xml, order.hbm.xml I have received the following error while trying the table per subclass mapping and tried a join table mapping in the parent class. If it does not have an inheritance relation then it works fine. The table mentioned below is being created hibernate ------------------------------------------------------------------------------------------------------------------------------ org.hibernate.AssertionFailure: Table WK_CONTACT not found at org.hibernate.persister.entity.JoinedSubclassEntityPersister.getTableId(JoinedSubclassEntityPersister.java:458) at org.hibernate.persister.entity.JoinedSubclassEntityPersister.<init>(JoinedSubclassEntityPersister.java:237) at org.hibernate.persister.PersisterFactory.createClassPersister(PersisterFactory.java:58) at org.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:226) at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1294) at com.metaarchit.bookshop.HibernateUtil.init(HibernateUtil.java:19) at com.metaarchit.bookshop.HibernateUtil.getSessionFactory(HibernateUtil.java:33) at com.metaarchit.bookshop.HibernateTest.insert(HibernateTest.java:123) at com.metaarchit.bookshop.HibernateTest.main(HibernateTest.java:26) null ------------------------------------------------------------------------------------------------------------------------------ -- 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

1
1
0 / 0

[Hibernate-JIRA] Commented: (HHH-1724) Critieria needs to be aligned with new aggreation type rules

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1724?page=c... ] Steve Ebersole commented on HHH-1724: ------------------------------------- I'd prefer it to be symmetric with HQL. Basically have a single contract from which HQL and Criteria queries figure out the return type for the various aggregation functions. And then allow that thing to be swapped. Sound reasonable? > Critieria needs to be aligned with new aggreation type rules > ------------------------------------------------------------ > > Key: HHH-1724 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1724 > Project: Hibernate Core > Issue Type: Bug > Components: core > Reporter: Max Rydahl Andersen > Assignee: Steve Ebersole > Priority: Blocker > Fix For: 3.5 > > > Criteria does not ask the dialect about the type + it does not always seem to know what the underlying field type is..... > created as blocker to make sure we either document or fix 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, 10 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-3943) Criteria fails to search ManyToMany associations while setCacheable is true

by TK Kocheran (JIRA)

Criteria fails to search ManyToMany associations while setCacheable is true --------------------------------------------------------------------------- Key: HHH-3943 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3943 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.3.1 Environment: MySQL 5, Hibernate 3.3.1 Reporter: TK Kocheran When using the Criteria API to search for values in ManyToMany associations, if setCacheable is true, Hibernate will fail to find certain objects. I have confirmed this problem both when using unidirectional and bidirectional ManyToMany associations. The scenario kind of looks like this: @Entity @Table(name='group') public class Group { ... @ManyToMany(targetEntity=User.class) @JoinTable(name="group_members") private List<User> members; ... } When searching for specific groups, I will often form criteria like this: Criteria criteria = session.createCriteria(SupportGroup.class) .setTimeout(10) .setCacheable(true) .createAlias("members", "members") .add(Restrictions.eq("members.username", "tomSawyer")); Executing this criteria will fail to retrieve any results. Only when setCacheable is set to false will results be returned. (I have confirmed through other means that I can get access to the entities matching these restrictions) -- 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

1
1
0 / 0

[Hibernate-JIRA] Assigned: (HHH-1724) Critieria needs to be aligned with new aggreation type rules

by Max Rydahl Andersen (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1724?page=c... ] Max Rydahl Andersen reassigned HHH-1724: ---------------------------------------- Assignee: Steve Ebersole (was: Max Rydahl Andersen) As I remember to fix it was pretty straightforward, but since it would have broken *a lot* of users criteria queries we didn't do it. It will also break a lot now, but with a 3.5 it might be tolerable....maybe provide a "legacy criteria mapping option" ? (maybe it is possible to support by custom dialect type returns ? > Critieria needs to be aligned with new aggreation type rules > ------------------------------------------------------------ > > Key: HHH-1724 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1724 > Project: Hibernate Core > Issue Type: Bug > Components: core > Reporter: Max Rydahl Andersen > Assignee: Steve Ebersole > Priority: Blocker > Fix For: 3.5 > > > Criteria does not ask the dialect about the type + it does not always seem to know what the underlying field type is..... > created as blocker to make sure we either document or fix 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, 10 months

1
0
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 2009