September 2009 - hibernate-issues

[Hibernate-JIRA] Created: (HHH-3884) NPE with mutable Natuarl Id's

by Michael Kopp (JIRA)

NPE with mutable Natuarl Id's ----------------------------- Key: HHH-3884 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3884 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.2.2 Reporter: Michael Kopp When saving an entity with a mutable natural id hibernate throws the following NPE. java.lang.NullPointerException at org.hibernate.engine.StatefulPersistenceContext.getNaturalIdSnapshot(StatefulPersistenceContext.java:267) at org.hibernate.event.def.DefaultFlushEntityEventListener.checkNaturalId(DefaultFlushEntityEventListener.java:78) at org.hibernate.event.def.DefaultFlushEntityEventListener.getValues(DefaultFlushEntityEventListener.java:162) at org.hibernate.event.def.DefaultFlushEntityEventListener.onFlushEntity(DefaultFlushEntityEventListener.java:113) at org.hibernate.event.def.AbstractFlushingEventListener.flushEntities(AbstractFlushingEventListener.java:196) at org.hibernate.event.def.AbstractFlushingEventListener.flushEverythingToExecutions(AbstractFlushingEventListener.java:76) at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:26) at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:1000) I checked the code and found the reason: - getNaturalIdSnapshot calls getDatabaseSnapshot and checks the result for NO_ROW but not for null - getDatabaseSnapshot will never return NO_ROW but null if nothing was found hence getNaturalIdSnapshot will produce a NPE if the entity is not in the database already. the fix is simple: change: Object[] entitySnapshot = getDatabaseSnapshot( id, persister ); if ( entitySnapshot == NO_ROW ) { return null; } to Object[] entitySnapshot = getDatabaseSnapshot( id, persister ); if ( entitySnapshot == null ) { return null; } This is still there in trunk 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

15 years, 11 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HHH-3068) Update of an entity with immutable natural-id and many-to-one relation seems to fail

by Pascal Cohen (JIRA)

Update of an entity with immutable natural-id and many-to-one relation seems to fail ------------------------------------------------------------------------------------ Key: HHH-3068 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3068 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.5 Environment: Hibernate 3.2.5 Linux Fedora 32bits Postgres 8.2.5 Reporter: Pascal Cohen Priority: Minor I have posted in the forum the following question and someone seems to confirm this might be a bug. http://forum.hibernate.org/viewtopic.php?t=982385&highlight= Thanks in advance for advice -- 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, 11 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2041) Update with unaltered natural-id fails

by Jim Pease (JIRA)

Update with unaltered natural-id fails -------------------------------------- Key: HHH-2041 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2041 Project: Hibernate3 Type: Bug Components: core Versions: 3.1.3 Environment: hibernate-3.1.3, mysql-4.1.12 Reporter: Jim Pease This may be a duplicate of http://opensource.atlassian.com/projects/hibernate/browse/HHH-1574. Getting following error: caused by: org.hibernate.HibernateException: immutable natural identifier of an instance of edu.syr.lsb.gmt.impl.LinkImpl was altered at org.hibernate.event.def.DefaultFlushEntityEventListener.checkNaturalId(DefaultFlushEntityEventListener.java:80) at org.hibernate.event.def.DefaultFlushEntityEventListener.getValues(DefaultFlushEntityEventListener.java:155) at org.hibernate.event.def.DefaultFlushEntityEventListener.onFlushEntity(DefaultFlushEntityEventListener.java:106) at org.hibernate.event.def.AbstractFlushingEventListener.flushEntities(AbstractFlushingEventListener.java:195) at org.hibernate.event.def.AbstractFlushingEventListener.flushEverythingToExecutions(AbstractFlushingEventListener.java:76) at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:26) ... This is occurring without modifications to the natural identifier, which is mapped as follows: <natural-id> <property name="activityRef" column="ACTIVITY_REF" length="255" not-null="true" /> <many-to-one name="goal" class="GoalImpl" column="GOAL_ID" not-null="true" cascade="none" /> </natural-id> -- 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, 11 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-3256) OptimizerFactory$PooledOptimizer.generate doesn't set keep the in-memory hi_value in sync with the db next_val (after a JBoss restart)

by Tom Muldoon (JIRA)

OptimizerFactory$PooledOptimizer.generate doesn't set keep the in-memory hi_value in sync with the db next_val (after a JBoss restart) -------------------------------------------------------------------------------------------------------------------------------------- Key: HHH-3256 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3256 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.6 Environment: Hibernate 3.2.6, MySQL 5 Reporter: Tom Muldoon After a JBoss restart, the in-memory hiValue is -1. As such, the callback.getNextValue( ) method is invoked twice. With an increment size of 50 and a current database next_val of 10000, the PooledOptimizer.generate method returns a value of 10000 (as expected) and sets the in memory hiValue to 10050 (also as expected), however, it sets the db next_val to 10100. Shouldn't the db next_val be kept in sync with the in-memory hiValue (i.e. 10050)? -- 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, 11 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-324) @DynamicBoost(BoostStrategy.class)

by Emmanuel Bernard (JIRA)

@DynamicBoost(BoostStrategy.class) ---------------------------------- Key: HSEARCH-324 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-324 Project: Hibernate Search Issue Type: New Feature Components: mapping Reporter: Emmanuel Bernard Fix For: 3.1.1, 3.2.0 This sounds like an interesting feature. We could do something very similar to the new AnalyzerDiscriminator approach. The use case is explained http://saloon.javaranch.com/cgi-bin/ubb/ultimatebb.cgi?ubb=get_topic&f=78... Need some analysis before the jump We can do that in 3.1.1, but no hard pressure. -- 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, 11 months

4
9
0 / 0

[Hibernate-JIRA] Created: (HHH-4065) Incorrect SQL is used for HQL if the number of values for a filter collection parameter is changed

by Nicklas Nordborg (JIRA)

Incorrect SQL is used for HQL if the number of values for a filter collection parameter is changed -------------------------------------------------------------------------------------------------- Key: HHH-4065 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4065 Project: Hibernate Core Issue Type: Bug Components: query-hql Affects Versions: 3.3.2 Environment: Hibernate 3.3.2 Reporter: Nicklas Nordborg Attachments: trace.txt I think that maybe the fix for HHH-530 has introduced a problem with filters that has a collection-type parameter. If the number of parameters in that collection changes during the lifetime of a SessionFactory the SQL that is used becomes incorrect and either has too many or too few parameter placeholders (eg. '?') in the SQL. There was no problem in Hibernate 3.3.1. A typical error message is: java.sql.SQLException: Parameter index out of bounds. 2 is not between valid values of 1 and 1 Below is some pseudo-code that shows what happens when the number of values in a collection is increased from 1 to 2. The 'memberOf' is a simple filter on the `id` column: `id` IN (:items) String hql = "select n from NewsData n"; List idList = new ArrayList(); idList.add(1); Session s = .... // create new session s.enableFilter("memberOf").setParameterList("items", idList); s.createQuery(hql).list(); // SQL: select .... `News` newsdata0_ where newsdata0_.`id` IN (?) s.close(); idList.add(2); s = ... // create new session s.enableFilter("memberOf").setParameterList("items", idList); s.createQuery(hql).list(); // <--- error here with 3.3.2 but works with 3.3.1 // SQL (3.3.2): select .... `News` newsdata0_ where newsdata0_.`id` IN (?) // SQL (3.3.1): select .... `News` newsdata0_ where newsdata0_.`id` IN (?, ?) I am attaching a file with TRACE-level output from both Hibernate 3.3.2 and 3.3.1. The relevant difference seems to be that in Hibernate 3.3.2 the query plan is cached with: [SQL_TOKEN] SqlFragment: 'newsdata0_.`id` IN (?)' but in Hibernate 3.3.1 with: [SQL_TOKEN] SqlFragment: 'newsdata0_.`id` IN (:memberOf.items)' -- 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, 11 months

5
14
0 / 0

[Hibernate-JIRA] Created: (EJB-463) Merging of one-to-many relations not JPA spec compliant for lazy relations

by Dirk (JIRA)

Merging of one-to-many relations not JPA spec compliant for lazy relations -------------------------------------------------------------------------- Key: EJB-463 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-463 Project: Hibernate Entity Manager Issue Type: Bug Affects Versions: 3.4.0.GA Environment: Hibernate 3.2.6, Hibernate EntityManager 3.4.0, Hibernate Annotations 3.4.0, Oracle Reporter: Dirk Attachments: CascadeTest.zip Topic has been posted to the Hibernate Forum. See https://forum.hibernate.org/viewtopic.php?f=1&t=999398 Summary: Suppose you have an object Master with one-to-many relation to Detail. @Entity public class Master implements Serializable { @OneToMany(mappedBy = "master", cascade={CascadeType.MERGE, CascadeType.PERSIST}) private List<Detail> details = new ArrayList<Detail>(); ... } Master is loaded without fetching Detail (= lazy) and EntityManager is closed. Master is now in detached state. Merging Master causes Hibernate EntityManager to eagerly load the Detail collection although it is in lazy state. This is not JPA spec compliant. JPA spec states: The persistence provider must not merge fields marked LAZY that have not been fetched: it must ignore such fields when merging. See 3.2.4.1 Merging Detached Entity State, p.51. Tested also with the latest version of EclipseLink. EclipseLink behaves as expected. Testcase attached (Netbeans 6.7). -- 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, 11 months

4
4
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-333) Remove or improve log warning in DocumentBuilderContainedEntity.checkDocumentId

by Hardy Ferentschik (JIRA)

Remove or improve log warning in DocumentBuilderContainedEntity.checkDocumentId ------------------------------------------------------------------------------- Key: HSEARCH-333 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-333 Project: Hibernate Search Issue Type: Bug Components: engine Affects Versions: 3.1.0.GA Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik Fix For: 3.1.1 http://forum.hibernate.org/viewtopic.php?t=993097 -- 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, 11 months

3
7
0 / 0

[Hibernate-JIRA] Created: (HHH-1992) Some cascade actions should not trigger a property access on lazy properties

by Emmanuel Bernard (JIRA)

Some cascade actions should not trigger a property access on lazy properties ---------------------------------------------------------------------------- Key: HHH-1992 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1992 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.0.cr3 Reporter: Emmanuel Bernard Assigned to: Emmanuel Bernard Priority: Critical Fix For: 3.2.0.ga -- 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, 11 months

3
4
0 / 0

[Hibernate-JIRA] Created: (HHH-3107) Error with sql generated for set of subclass A in a peer subclass B.

by Austin Mayberry (JIRA)

Error with sql generated for set of subclass A in a peer subclass B. -------------------------------------------------------------------- Key: HHH-3107 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3107 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.2.6 Reporter: Austin Mayberry A mapping such as the following contrived examples does not yield the expected results and causes and error: <class name="com.foo.Foo1" table="FOO1"> <id name="id" type="java.lang.Integer" column="ID" > <generator class="sequence" > <param name="sequence">ID_SEQ</param> </generator> </id> <discriminator column="FOO_TYPE_ID" type="java.lang.Integer"/> <subclass name="com.foo.Foo2" discriminator-value="0"> <join table="FOO2"> <key column="ID"/> <property name="label" type="java.lang.String" column="LABEL" not-null="true" length="255" /> </join> <subclass name="com.foo.BarOne" discriminator-value="1"> <set name="barTwos" inverse="true" > <key> <column name="PARENT_ID" /> </key> <one-to-many class="com.foo.BarTwo" /> </set> </subclass> <subclass name="com.foo.BarTwo" discriminator-value="2"> <join table="BAR"> <key column="ID"/> <many-to-one name="parent" class="com.foo.BarOne" not-null="true" column="PARENT_ID" /> </join> </subclass> </subclass> </class> The sql created to populate the set "bartwos" looks like this looks like: select bartwos0_.PARENT_ID as PA3_1_, bartwos0_.ID as ID1_1_, bartwos0_.ID as ID1_52_0_, bartwos0_.FOO_TYPE_ID as FO2_52_0_, bartwos0_1_.LABEL as LABEL76_0_, bartwos0_2_.PARENT_ID as PA2_87_0_ from FOO1 bartwos0_, FOO2 bartwos0_1_, BAR2 bartwos0_2_ where bartwos0_.ID=bartwos0_1_.ID and bartwos0_.ID=bartwos0_2_.ID and bartwos0_.PARENT_ID=? And yields the following error message: java.sql.SQLException: ORA-00904: "BARTWOS0_"."PARENT_ID: invalid identifier The basic problem is that it should be looking for the property PARENT_ID on BAR2, but it is looking for it on FOO1. -- 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, 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 September 2009