September 2009 - hibernate-issues

[Hibernate-JIRA] Created: (HHH-2975) Interceptor onFlushDirty collections - previous and current state the same instance

by Clayton J. Kovar (JIRA)

Interceptor onFlushDirty collections - previous and current state the same instance ----------------------------------------------------------------------------------- Key: HHH-2975 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2975 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.2 Environment: Hibernate 3.2.2 - Oracle thin driver 10.1.0.4.0 Reporter: Clayton J. Kovar When calling Session.merge(entity) {therefore the previous state is available} the interceptor's onFlushDirty is called and the previous state for all of the simple properties correctly passes the previous values but with a collection the same collection instance is passed in both the previous and current state arrays. So far I have only seen this behavior on a Map with a one-to-many relationship to another entity. I have not tried it yet with Lists, Sets, or Bags. I'm assuming this is not expected behavior, but please let me know if it is. Best regards. -- 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

14 years, 8 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2862) Collection is not associated with any session exception when doing an eager fetch on a non-unique collection.

by Paul Andrews (JIRA)

Collection is not associated with any session exception when doing an eager fetch on a non-unique collection. ------------------------------------------------------------------------------------------------------------- Key: HHH-2862 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2862 Project: Hibernate3 Issue Type: Bug Environment: Hibernate 3.1.3 - Hibernate 3.2.5, HSQLDB, Java5 Reporter: Paul Andrews It is basically caused by having an eager collection where the key of the collection is not unique in the results. The code works as follows in CollectionType.getCollection(): .... persistenceContext.addUninitializedCollection( persister, collection, key ); // some collections are not lazy: if ( initializeImmediately( entityMode ) ) { session.initializeCollection( collection, false ); } else if ( !persister.isLazy() ) { persistenceContext.addNonLazyCollection( collection ); } if ( hasHolder( entityMode ) ) { session.getPersistenceContext().addCollectionHolder( collection ); } if persistenceContext.addUninitializedCollection() detects that the collection with the given key has already been added it clears the session on the old instance of the collection (sets it to null). However, that collection has already been added to the persistence context by an earlier call to this method. So later when StatefulPersistenceContext.initializeNonLazyCollections() is called it iterates through all of the collections in the persistence context (including those which have had their session set to null by addUninitializedCollection()), calling forceInitialization() which throws a 'collection is not associated with any session' exception. -- 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

14 years, 8 months

10
11
0 / 0

[Hibernate-JIRA] Created: (HHH-3695) RegionFactory's no-arg constructor does not get invoked

by Paul Cowan (JIRA)

RegionFactory's no-arg constructor does not get invoked ------------------------------------------------------- Key: HHH-3695 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3695 Project: Hibernate Core Issue Type: Bug Components: caching (L2) Affects Versions: 3.3.1 Reporter: Paul Cowan Priority: Trivial RegionFactory's class Javadoc says: * Implementors should define a constructor in one of two forms:<ul> * <li>MyRegionFactoryImpl({@link java.util.Properties})</li> * <li>MyRegionFactoryImpl()</li> * </ul> but SettingsFactory.createRegionFactory only looks for the one that takes a Properties class. This is relatively minor, I don't think 'fixing' this by just correcting the javadoc is really that big a deal but have patches for both ways. -- 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

14 years, 9 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-1985) NodeTraverser is not SOE-safe

by Sergey Vladimirov (JIRA)

NodeTraverser is not SOE-safe ----------------------------- Key: HHH-1985 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1985 Project: Hibernate3 Type: Improvement Components: core Versions: 3.2.0.cr3 Reporter: Sergey Vladimirov Priority: Minor org.hibernate.hql.ast.util.NodeTraverser It is possible for java.lang.StackOverflowError to occur in NodeTraverser.java:41;42 with very deep tree. Need another algorith to visit whole tree. 08.08 19:50:09 ERROR [ArpSiteServlet] Servlet.service() for servlet ArpSiteServlet threw exception java.lang.StackOverflowError at org.hibernate.hql.ast.util.NodeTraverser.visitDepthFirst(NodeTraverser.java:41) at org.hibernate.hql.ast.util.NodeTraverser.visitDepthFirst(NodeTraverser.java:41) at org.hibernate.hql.ast.util.NodeTraverser.visitDepthFirst(NodeTraverser.java:42) at org.hibernate.hql.ast.util.NodeTraverser.visitDepthFirst(NodeTraverser.java:42) at org.hibernate.hql.ast.util.NodeTraverser.visitDepthFirst(NodeTraverser.java:42) at org.hibernate.hql.ast.util.NodeTraverser.visitDepthFirst(NodeTraverser.java:42) -- 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

14 years, 9 months

7
9
0 / 0

[Hibernate-JIRA] Created: (HBX-869) SchemaUpdateTask does not actually APPLY the DDL on Mysql 5.0

by Schwark Satyavolu (JIRA)

SchemaUpdateTask does not actually APPLY the DDL on Mysql 5.0 ------------------------------------------------------------- Key: HBX-869 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-869 Project: Hibernate Tools Type: Bug Components: ant Versions: 3.2beta9 Environment: Mysql 5.0, windows Reporter: Schwark Satyavolu Priority: Critical The ant task in verbose mode shows that the table does not exist, prints the ddl for the create table, but in fact does NOT create the table. Yet, the build is reported successful. -- 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

14 years, 9 months

3
2
0 / 0

[Hibernate-JIRA] Created: (HV-76) Field annotated member validators does not work with proxied objects

by Lucien Weller (JIRA)

Field annotated member validators does not work with proxied objects --------------------------------------------------------------------- Key: HV-76 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-76 Project: Hibernate Validator Issue Type: Bug Affects Versions: 3.1.0.CR1, 3.0.0.ga Reporter: Lucien Weller Attachments: proxy-fix.patch, testcase.tar.gz Copied from subtask HV-68 as subtask of closed issue HV-64 seams not to appear as open issue): May be annotating validation constraints on field level ist not the best solution, but by now it's explicitly mentioned as a possibility without other indication of restrictions in hibernate validator doc. But obviously this method is not safe with hibernate proxy instances as it is demonstrated be test case attached to original issue (http://opensource.atlassian.com/projects/hibernate/secure/attachment/1409...). My first patch was a quick fix that worked for our case and a agree once again that it may have some side effects as it changes the semantic of field annotation. but my second solution (http://opensource.atlassian.com/projects/hibernate/secure/attachment/1409...) leaves every thing as it is and just handles proxy instances differently and produce a more correct validation result than in current version. I hope that you can do something with my ideas or a least document this limitation when using field annotation. -- 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

14 years, 9 months

4
5
0 / 0

[Hibernate-JIRA] Created: (HHH-2288) Adding a new ResultTransformer, permitting to instantiate and fill related beans and not to take care of aliases case.

by Nicolas Billard (JIRA)

Adding a new ResultTransformer, permitting to instantiate and fill related beans and not to take care of aliases case. ---------------------------------------------------------------------------------------------------------------------- Key: HHH-2288 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2288 Project: Hibernate3 Type: Improvement Components: query-sql, query-hql, query-criteria Versions: 3.2.1 Environment: Developped based on hibernate v 3.2.1 Reporter: Nicolas Billard Priority: Minor Attachments: ResultTransformerImprovement.zip Are joined to this post 2 classes. Below is the javadoc header of the ResultTransformer class. May be this could be integrated in next hibernate versions ( certainly with improvements ... :p ) Let me know if anyone finds it useful ... ------------------------------------------------------ * Transforms resultset to value a bean, via setters. * * Examples: * * bean MyBean as 2 setters : * - setId : takes an Integer * - setProduct : takes a Product bean * * Product bean as 2 setters : * - setId * - setLib * * resultset may have these columns : * - ID * - PRODUCT_ID * - PRODUCT_LIB * * A MyBean instance will be created for each tupple, * and a Product instance will be also created, filled with PRODUCT_ID and PRODUCT_LIB values. -- 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

14 years, 9 months

3
8
0 / 0

[Hibernate-JIRA] Created: (HHH-3743) MININDEX function applied on entity of many-to-many mapped collection yields incorrect SQL

by Stefan Wachter (JIRA)

MININDEX function applied on entity of many-to-many mapped collection yields incorrect SQL ------------------------------------------------------------------------------------------ Key: HHH-3743 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3743 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.1 Environment: Hibernate 3.3.1, org.hibernate.dialect.DerbyDialect and org.hibernate.dialect.MySQLInnoDBDialect Reporter: Stefan Wachter I have a "t_Person" entity with a "many-to-many" list to a "t_Address" entity: <class entity-name="t_Person" table="F5_T_PERSON" lazy="true"> <id name="_id" column="ID" type="long"> <generator class="native"/> </id> <list lazy="true" cascade="all" name="elemAddress" table="F5_T_PERSON_ELM_ADDRESS"> <key column="OWNER_KEY"/> <list-index column="IDX"/> <many-to-many column="FOREIGN_KEY" entity-name="t_Address"/> </list> </class> <class entity-name="t_Address" table="F5_T_ADDRESS" lazy="true"> <id name="_id" column="ID" type="long"> <generator class="native"/> </id> <property name="attrStreet" type="string"> <column name="A_STREET"/> </property> </class> When I try to retrieve the minimum index of address entities using the following HQL select MININDEX(a) from t_Person as p join p.elemAddress as a incorrect SQL results: select min(t_address2_.IDX) as col_0_0_ from F5_T_PERSON t_person0_ inner join F5_T_PERSON_ELM_ADDRESS elemaddres1_ on t_person0_.ID=elemaddres1_.OWNER_KEY inner join F5_T_ADDRESS t_address2_ on elemaddres1_.FOREIGN_KEY=t_address2_.ID In particular the addressed column "t_address2_.IDX" does not exists. Instead "elemaddres1_.IDX" should be used because the index column is contained in the join table "F5_T_PERSON_ELM_ADDRESS". I assume that the MININDEX function does not consider the case when it is applied to an element of a many-to-many collection. I tested this with the DerbyDialect and the MySQLInnoDBDialect. -- 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

14 years, 9 months

2
1
0 / 0

[Hibernate-JIRA] Created: (EJB-387) The EntityManager.lock() uses the wrong column name when it is passed a sub-type entity from a joined inheritance strategy

by mike wray (JIRA)

The EntityManager.lock() uses the wrong column name when it is passed a sub-type entity from a joined inheritance strategy -------------------------------------------------------------------------------------------------------------------------- Key: EJB-387 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-387 Project: Hibernate Entity Manager Issue Type: Bug Components: EntityManager Affects Versions: 3.4.0.GA Environment: Hibernate 3.3.1 Annotations 3.4 Reporter: mike wray Priority: Minor I would expect to see: update SUPER set ROW_VERSION_SEQ=? where SUPER_ID=? and ROW_VERSION_SEQ=? but instead I see: update SUPER set ROW_VERSION_SEQ=? where SUB_ID=? and ROW_VERSION_SEQ=? which throws a org.hibernate.exception.SQLGrammarException: could not retrieve version. This is because column SUB_ID does not exist on table SUPER. -- 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

14 years, 9 months

4
3
0 / 0

[Hibernate-JIRA] Created: (HHH-3938) One-To-One Filter Applied, Non-Lazy Fetch Problem

by Sandeep Vaid (JIRA)

One-To-One Filter Applied, Non-Lazy Fetch Problem ------------------------------------------------- Key: HHH-3938 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3938 Project: Hibernate Core Issue Type: Improvement Components: core Affects Versions: 3.3.1 Reporter: Sandeep Vaid Priority: Critical Suppose i have one-to-one association between Product and ProductBasic. and we have applied filter on ProductBasic Class. I have applied this filter as in Java side we have one-to-one relationship between Product and ProductBasic BUT at database side we have one-to-many relationship between PRODUCT and PRODUCTBASIC. and we apply a condition (STARTTIME < CURRETTIME < ENDTIME) while fetching PRODUCTBASIC, and this will always give me one record out of many. So i have put this condition as filter in ProductBasic class. In current hibernate, one-to-one associations are always non-lazily fetched. Moreover it doesn't apply filter conditions. I understand that it can;t apply filter condition as some filter parameter must be provided at runtime and user may not provide them (as he is not asking for ProductBasic)... Also in this case, proper proxy can't be created as until we apply the filter criteria, we won't get one ProductBasic row (among many).. I think hibernate code should be changed so that if a filter is declared on the associated class (ProductBasic in our case), hibernate should return null for ProductBasic. -- 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

14 years, 9 months

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues September 2009