January 2010 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-3817) JBC second level cache integration can cache collection data

by Brian Stansberry (JIRA)

JBC second level cache integration can cache collection data ------------------------------------------------------------ Key: HHH-3817 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3817 Project: Hibernate Core Issue Type: Bug Components: caching (L2) Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 3.3.x Scenario with two transactions dealing with a single collection: tx1 reads collection, cache miss tx1 goes to database to read collection tx2 reads collection, cache miss tx2 goes to database to read collection tx2 does JBC putForExternalRead to store empty collection tx2 updates collection tx2 removes collection from JBC (since any collection update triggers a org.hibernate.cache.Cache.evict which is implemented as a JBC removeNode) tx1 does JBC putForExternalRead to store empty collection -- STALE DATA With entities, if the db is using REPEATABLE_READ this won't be a problem, as the DB won't allow the tx2 update until tx1 commits. With a collection there is nothing to lock on. It would be a problem for entities with READ_COMMITTED as well. -- 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
7
0 / 0

[Hibernate-JIRA] Created: (HHH-4606) Add support for @*ToOne @JoinTable in XML

by Emmanuel Bernard (JIRA)

Add support for @*ToOne @JoinTable in XML ----------------------------------------- Key: HHH-4606 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4606 Project: Hibernate Core Issue Type: Sub-task Reporter: Emmanuel Bernard -- 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
8
0 / 0

[Hibernate-JIRA] Created: (HHH-4605) Add support for @OneToMany @JoinColumn in XML

by Emmanuel Bernard (JIRA)

Add support for @OneToMany @JoinColumn in XML --------------------------------------------- Key: HHH-4605 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4605 Project: Hibernate Core Issue Type: Sub-task Reporter: Emmanuel Bernard -- 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
17
0 / 0

[Hibernate-JIRA] Created: (HHH-4810) Persistent immutable and read-only entities are updated before being deleted

by Gail Badner (JIRA)

Persistent immutable and read-only entities are updated before being deleted ---------------------------------------------------------------------------- Key: HHH-4810 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4810 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.0-Beta-3 Reporter: Gail Badner Assignee: Gail Badner Fix For: 3.5.0-Beta-4 Read-only and immutable entities that are in persistent state when deleted are updated before being deleted. Read-only and immutable entities that are detached when deleted are not updated before being deleted. In the following examples, Contract is an immutable class. Example 1: Immutable entity is updated with the same property values as just read s = openSession(); t = s.beginTransaction(); c = (Contract) s.get( Contract.class, c.getId() ); s.delete(c); t.commit(); s.close(); Hibernate: update Contract set customerName=?, type=? where id=? 17:59:32,640 TRACE StringType:151 - binding 'gavin' to parameter: 1 17:59:32,640 TRACE StringType:151 - binding 'phone' to parameter: 2 17:59:32,641 TRACE LongType:151 - binding '1' to parameter: 3 ... (immutable collection, Contract.getVariations() is also updated and deleted) Hibernate: delete from Contract where id=? 17:59:32,654 TRACE LongType:151 - binding '1' to parameter: 1 ------------------------------------------------------------------------- Example 2: Immutable entity is updated with a new property value before being deleted s = openSession(); t = s.beginTransaction(); c = (Contract) s.get( Contract.class, c.getId() ); c.setCustomerName( "Sherman" ); s.delete(c); t.commit(); s.close(); Hibernate: update Contract set customerName=?, type=? where id=? 17:59:33,221 TRACE StringType:151 - binding 'Sherman' to parameter: 1 17:59:33,221 TRACE StringType:151 - binding 'phone' to parameter: 2 17:59:33,222 TRACE LongType:151 - binding '6' to parameter: 3 ... (immutable collection, Contract.getVariations() is also updated and deleted) Hibernate: delete from Contract where id=? 17:59:33,242 TRACE LongType:151 - binding '6' to parameter: 1 Example 3: No update when the immutable entity is detached when it is deleted. s = openSession(); t = s.beginTransaction(); s.delete( c ); t.commit(); s.close(); ... (immutable collection, Contract.getVariations() is deleted) Hibernate: delete from Contract where id=? 17:59:33,337 TRACE LongType:151 - binding '8' to parameter: 1 -- 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
6
0 / 0

[Hibernate-JIRA] Created: (HHH-4825) mapping order impacting behavior leading to bug

by Anthony Patricio (JIRA)

mapping order impacting behavior leading to bug ----------------------------------------------- Key: HHH-4825 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4825 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.2 Reporter: Anthony Patricio Following mapping fails: <hibernate-mapping default-access="property" package="case419703"> <class abstract="false" dynamic-insert="true" dynamic-update="true" name="TestB" table="TEST_B"> <composite-id class="case419703.key.FrameworkKeyCustID" name="frameworkKey"> <key-property column="NR_RZBK" name="frameworkCustId"/> <key-property column="TXT_OID" name="frameworkOid"/> </composite-id> <version column="NR_VERSION" name="frameworkVersion"/> <set cascade="persist, merge, save-update" inverse="true" lazy="true" name="testC"> <key> <column name="NR_RZBK"/> <column name="TXT_OID_TESTB"/> </key> <one-to-many class="TestC"/> </set> </class> <class abstract="true" dynamic-insert="true" dynamic-update="true" name="AbstractTestC" table="notable"> <composite-id class="case419703.key.FrameworkKeyCustID" name="frameworkKey"> <key-property column="NR_RZBK" name="frameworkCustId"/> <key-property column="TXT_OID" name="frameworkOid"/> </composite-id> <version column="NR_VERSION" name="frameworkVersion"/> <union-subclass dynamic-insert="true" dynamic-update="true" name="case419703.TestC" table="TEST_C"> <property column="PID" name="pid" update="false"/> <property column="TXT_OID_TESTB" name="fkReverseTestB"/> <many-to-one cascade="persist, merge, save-update" class="case419703.TestB" fetch="select" insert="false" lazy="no-proxy" name="reverseTestB" update="false" > <column name="NR_RZBK" /> <column name="TXT_OID_TESTB" />  </many-to-one> </union-subclass> </class> </hibernate-mapping> however changing to <many-to-one cascade="persist, merge, save-update" class="case419703.TestB" fetch="select" insert="false" lazy="no-proxy" name="reverseTestB" update="false" > <column name="NR_RZBK" /> <column name="TXT_OID_TESTB" />  </many-to-one> <property column="PID" name="pid" update="false"/> <property column="TXT_OID_TESTB" name="fkReverseTestB"/> works. Something is wrong with th algo. See attached testcase. -- 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
12
0 / 0

[Hibernate-JIRA] Created: (ANN-660) HHH-2545 Alive

by Eugene Batogov (JIRA)

HHH-2545 Alive -------------- Key: ANN-660 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-660 Project: Hibernate Annotations Issue Type: Bug Affects Versions: 3.3.0.ga Environment: Gentoo Linux x86 JDK: 1.6. SUN and BEA JBoss-4.2.1.GA Hibernate: 3.2.5 Annotation: 3.3.0.GA EntityManager: 3.3.1 Reporter: Eugene Batogov Priority: Critical I have a same problem how in HHH-2545 bug ! I update Hibernate to 3.2.5, hibernate-annotation to 3.3.0.GA hibernate-entitymanager to 3.3.1.GA. But this bug alive! I use ehcache-1.3.0. jBoss-4.2.1.GA. My query, which get from cache with null elements in collections: Long customerAccount = customerIdentity.getCustomerAccount().getId(); try{ String sql = "select npvr.npvrChannels from NpvrServiceSpec npvr"+ " where npvr.id in ("+ " select ss.id from Customer cust join cust.accounts acc join cust.subscriptions sub"+ " join sub.serviceSpecifications ss"+ " where acc.id =:customerAccount and"+ " ss in (from NpvrServiceSpec))"; Query query = emanager.createQuery(sql); query.setParameter("customerAccount", customerAccount); query.setHint("org.hibernate.cacheRegion", "query.findQueryNpvrChannelsBySubsription"); query.setHint("org.hibernate.cacheable", true); result = query.getResultList(); Help me, please ! Thanks in advance. -- 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

5
12
0 / 0

[Hibernate-JIRA] Created: (HHH-4845) Investigate why entitymanager test cannot be run in forkMode once

by Hardy Ferentschik (JIRA)

Investigate why entitymanager test cannot be run in forkMode once ----------------------------------------------------------------- Key: HHH-4845 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4845 Project: Hibernate Core Issue Type: Bug Components: build, entity-manager Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik Fix For: 3.5 Currently the forkMode for the entitymanager module is once. To improve the build speed it would be nice to only fork once. However, forking once triggers some test failures. The initial thought was that the tests which rely on packages (war, par, etc ...) cause the problem. A solution for this could be http://docs.codehaus.org/display/MAVENUSER/Maven+and+Integration+Testing Looking at the actual failing tests might indicate another problem though. The failing tests are: {code} Failed tests: testCreateExceptionWithGeneratedId(org.hibernate.ejb.test.ops.PersistTest) Tests in error: testFlushOnDetached(org.hibernate.ejb.test.emops.FlushTest) testSerialization(org.hibernate.ejb.test.ejb3configuration.EntityManagerSerializationTest) Tests run: 182, Failures: 1, Errors: 2, Skipped: 0 {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, 1 month

3
4
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-53) Add support for projection (ie read the data from the index only)

by Emmanuel Bernard (JIRA)

Add support for projection (ie read the data from the index only) ----------------------------------------------------------------- Key: HSEARCH-53 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-53 Project: Hibernate Search Issue Type: New Feature Components: query Reporter: Emmanuel Bernard Assignee: Emmanuel Bernard Fix For: 3.0.0.beta2 -- 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
2
0 / 0

[Hibernate-JIRA] Created: (HHH-4662) Implement javax.persistence.query.timeout

by Emmanuel Bernard (JIRA)

Implement javax.persistence.query.timeout ----------------------------------------- Key: HHH-4662 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4662 Project: Hibernate Core Issue Type: Sub-task Reporter: Emmanuel Bernard -- 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
12
0 / 0

[Hibernate-JIRA] Created: (HHH-4676) Any interceptor exception (RTE) should mark the tx for rollback

by Emmanuel Bernard (JIRA)

Any interceptor exception (RTE) should mark the tx for rollback --------------------------------------------------------------- Key: HHH-4676 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4676 Project: Hibernate Core Issue Type: Sub-task Reporter: Emmanuel Bernard -- 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
9
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 January 2010