September 2006 - hibernate-issues

[Hibernate-JIRA] Created: (HHH-2066) HSQL DB + multi-schema --> raised an exception (Problem to get an increment key [select max(id) from table)

by XOrangOutan (JIRA)

HSQL DB + multi-schema --> raised an exception (Problem to get an increment key [select max(id) from table) ----------------------------------------------------------------------------------------------------------- Key: HHH-2066 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2066 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.0.cr4 Environment: HSQL DB 1.8.x Reporter: XOrangOutan When trying to save an object that has an "incremental" primary key, Hibernate API tries to know what the max current id is by executing a "SELECT MAX". Though, in this particular sql query, schema name is not taken into account (in hsqldialect). This cause an error that prevents anyone from carrying out unit tests. This bug also exists on 3.x versions -- 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

15 years, 6 months

4
4
0 / 0

[Hibernate-JIRA] Created: (HBX-729) boolean types mapped to bit in MySQL 5 not working with EJB3 in JBoss 4.0.4.GA

by Daniel Pocock (JIRA)

boolean types mapped to bit in MySQL 5 not working with EJB3 in JBoss 4.0.4.GA ------------------------------------------------------------------------------ Key: HBX-729 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-729 Project: Hibernate Tools Type: Bug Versions: 3.2beta6 Environment: Debian Reporter: Daniel Pocock I define a property with type="boolean" in my .hbm.xml The generated SQL column defaults to bit(1). However, when using JBoss 4.0.4.GA and MySQL 5.0.22, reading the property (getXXX()) always return false If I force hbm2sql to generate a tinyint column, the boolean works as I would have expected: <column name="myColumn" sql-type="tinyint"/> -- 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

15 years, 7 months

4
3
0 / 0

[Hibernate-JIRA] Created: (HHH-2021) org.hibernate.cache.QueryKey has a fragile equals() method

by Kenny MacLeod (JIRA)

org.hibernate.cache.QueryKey has a fragile equals() method ---------------------------------------------------------- Key: HHH-2021 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2021 Project: Hibernate3 Type: Bug Components: core Versions: 3.1.3 Reporter: Kenny MacLeod Priority: Trivial This one is no great shakes, but the first line of QueryKey.equals() casts the argument to QueryKey without checking for its type. As such, the method is fragile. It should be consistent with CacheKey, which does an instanceof check before the cast. -- 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

15 years, 8 months

7
15
0 / 0

[Hibernate-JIRA] Created: (EJB-224) <exclude-unlisted-classes>false</exclude-unlisted-classes> has no effect on J2SE

by Sami Dalouche (JIRA)

<exclude-unlisted-classes>false</exclude-unlisted-classes> has no effect on J2SE --------------------------------------------------------------------------------- Key: EJB-224 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-224 Project: Hibernate Entity Manager Type: Bug Components: EntityManager Versions: 3.2.0.cr1 Environment: J2SE, JDK5 Versions : ----------- Hibernate Core 3.2.CR2 Hibernate Annotations 3.2.0 CR1 Hibernate Entity Manager 3.2.0 CR1 Reporter: Sami Dalouche When using the EntityManagerFactory from a webapplication (jetty), all my @Entity classes are detected, and mapped correctly. When running the same code from Eclipse (run java application), hibernate doesn't detect any of my @Entity. Everything works perfectly if I add all the corresponding <class> entries in persistence.xml. the following code : <persistence-unit ...> <exclude-unlisted-classes>false</exclude-unlisted-classes> </persistence-unit ...> does not seem to have any effect.. -- 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

15 years, 9 months

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

15 years, 10 months

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

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, 1 month

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, 1 month

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, 2 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-2110) Proxied object causes ClassCastException when method returns 'this' in a composite hierarchy

by Philip Nightingale (JIRA)

Proxied object causes ClassCastException when method returns 'this' in a composite hierarchy -------------------------------------------------------------------------------------------- Key: HHH-2110 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2110 Project: Hibernate3 Type: Bug Components: core Versions: 3.0.5 Environment: Hibernate 3, any database (test case uses HSQL, issue found using Oracle) Reporter: Philip Nightingale Attachments: HibernateClassCastExceptionTest.zip If a proxied object has a method that returns 'this' and the proxy type extends the same base class as the target object and the return type of the method is the target class type then a ClassCastException is thrown. The error can be tracked down to the method CGLibLazyInitializer::intercept(Object, Method, Object[], MethodProxy). In this method, if the object returned from the method call on the target object is the same as the target object, then instead of returning the object itself the proxy is returned. This is fine in most cases, but in the special case described, in which the proxy extends a base class that is also extended by the target class, then the CCE occurs. In the submitted test case I have a simple composite hierarchy with an abstract base type and two concrete subtypes. Either type can contain children, but only one can be the root of the hierarchy (and cannot itslef be a child). There is a many-to-one relationship defined from the sub-type that may be a child to the base class. The submitted test case is configured to use Hypersonic DB so hsqldb.jar is required on the classpath. Further details and code snippets from the original code that caused the exception are posted on the Hibernate user forum (topic "ClassCastException with CGLIB Lazy Initialization") -- 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, 4 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues September 2006