November 2006 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Resolved: (HHH-1564) Possible bug with deleting versioned object (patch included)

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1564?page=all ] Steve Ebersole resolved HHH-1564: --------------------------------- Resolution: Fixed trunk / 3.2 > Possible bug with deleting versioned object (patch included) > ------------------------------------------------------------ > > Key: HHH-1564 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1564 > Project: Hibernate3 > Type: Bug > Components: core > Versions: 3.1.2 > Environment: 3.1rc2 > Reporter: N Clayton > Assignee: Steve Ebersole > Fix For: 3.2.1 > Attachments: onetomanydelete_test.tar.gz > > > We're seeing an odd problem when trying to delete a row. The code that does this simply creates a new object, commits it, starts a new session, finds the object, deletes it. It dies with a constraint violation on an audit table, because hibernate is issuing an unnecessary update operation (and not incrementing the version either). Further debugging shows that Hibernate thinks that three properties on the object are 'modified'. These three are collections. One is the points collection, one owners and the other is systems. Hibernate seems to think that they are 'different' because null != an empty collection. So, it thinks it needs to update the object. However; later on - it doesn't increment the version number - because it knows the object is to be deleted. Thus - a problem. > A complete description is here: > http://forum.hibernate.org/viewtopic.php?t=950225&highlight=collectiontyp... > This appears to be fixed if we change CollectionType.isDirty() to be: > public boolean isDirty(Object old, Object current, boolean[] checkable, SessionImplementor session) > throws HibernateException { > if(checkable.length == 0) { > // Assume not checkable > return false; > } > return isDirty(old, current, session); > } -- 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

17 years, 7 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (ANN-37) @SqlInsert(), @SqlUpdate(), @SqlDelete(), @Loader()

by Emmanuel Bernard (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/ANN-37?page=com... ] Emmanuel Bernard commented on ANN-37: ------------------------------------- Guys, where did you learn that a feature without unit test is a feature ;-) > @SqlInsert(), @SqlUpdate(), @SqlDelete(), @Loader() > --------------------------------------------------- > > Key: ANN-37 > URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-37 > Project: Hibernate Annotations > Type: Improvement > Components: binder > Versions: 3.1beta3 > Reporter: Emmanuel Bernard > Priority: Trivial > Fix For: 3.2.1 > Attachments: custom_entity_loader.patch, customsqlannotations.patch, customsqlannotationsusingcheck.patch > > > @SqlInsert(statement="", callable=false), > @SqlUpdate(statement="", callable=false), > @SqlDelete(statement="", callable=false), > @Loader(namedQuery="") -- 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

17 years, 7 months

1
0
0 / 0

[Hibernate-JIRA] Created: (EJB-248) Wrap StaleStateException into an OptimisticLockException during em.getTransaction().commit()

by Emmanuel Bernard (JIRA)

Wrap StaleStateException into an OptimisticLockException during em.getTransaction().commit() -------------------------------------------------------------------------------------------- Key: EJB-248 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-248 Project: Hibernate Entity Manager Type: Improvement Components: EntityManager Versions: 3.2.0.ga Reporter: Emmanuel Bernard Assigned to: Emmanuel Bernard Priority: Minor Fix For: 3.2.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

17 years, 7 months

1
1
0 / 0

[Hibernate-JIRA] Commented: (HHH-1564) Possible bug with deleting versioned object (patch included)

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1564?page=c... ] Steve Ebersole commented on HHH-1564: ------------------------------------- This one comes down to a descrepency between the state as built by the DeleteEventListener (EntityEntry.deletedState) and the current values built during flush. Namely, the deletedState does not account for collections. Well, it would except that EntityPersister.getPropertyUpdateability() tells it to ignore them. The solution is to not rely on property-updateability when building an entity's deletedState. Conversely, I guess, we could also account for property-updateability when buidling current-values in the flush listener. I have not been able to recreate the issue of extra updates fired by inserting a parent. > Possible bug with deleting versioned object (patch included) > ------------------------------------------------------------ > > Key: HHH-1564 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1564 > Project: Hibernate3 > Type: Bug > Components: core > Versions: 3.1.2 > Environment: 3.1rc2 > Reporter: N Clayton > Assignee: Steve Ebersole > Fix For: 3.2.1 > Attachments: onetomanydelete_test.tar.gz > > > We're seeing an odd problem when trying to delete a row. The code that does this simply creates a new object, commits it, starts a new session, finds the object, deletes it. It dies with a constraint violation on an audit table, because hibernate is issuing an unnecessary update operation (and not incrementing the version either). Further debugging shows that Hibernate thinks that three properties on the object are 'modified'. These three are collections. One is the points collection, one owners and the other is systems. Hibernate seems to think that they are 'different' because null != an empty collection. So, it thinks it needs to update the object. However; later on - it doesn't increment the version number - because it knows the object is to be deleted. Thus - a problem. > A complete description is here: > http://forum.hibernate.org/viewtopic.php?t=950225&highlight=collectiontyp... > This appears to be fixed if we change CollectionType.isDirty() to be: > public boolean isDirty(Object old, Object current, boolean[] checkable, SessionImplementor session) > throws HibernateException { > if(checkable.length == 0) { > // Assume not checkable > return false; > } > return isDirty(old, current, session); > } -- 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

17 years, 7 months

1
0
0 / 0

[Hibernate-JIRA] Created: (EJB-247) HibernatePersistence does not play well with other PersistenceProviders

by Jeff Drost (JIRA)

HibernatePersistence does not play well with other PersistenceProviders ----------------------------------------------------------------------- Key: EJB-247 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-247 Project: Hibernate Entity Manager Type: Bug Components: EntityManager Versions: 3.2.0.ga Environment: all Reporter: Jeff Drost When HibernatePersistence is called to create a EntityManagerFactory, Ejb3Configuration.configure() is called. If configure() determines that persistence.xml refers to a non-hibernate provider, then it is not used, and null will be returned. HibernatePersistence never checks the return value of configure() and then calls buildEntityManagerFactory() - which will throw an exception. This stops javax.persistence.Persistence from searching for another provider. I would think HibernatePersistence should check the return value of configure() and only call buildEntityManagerFactory() if the result is non-null. Otherwise, null should be returned. -- 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

17 years, 7 months

2
1
0 / 0

[Hibernate-JIRA] Commented: (HHH-869) Querying collections of value type in the Criteria API

by Christian Bauer (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-869?page=co... ] Christian Bauer commented on HHH-869: ------------------------------------- Either attach a patch that implements what you want, or continue this on the forum. > Querying collections of value type in the Criteria API > ------------------------------------------------------ > > Key: HHH-869 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-869 > Project: Hibernate3 > Type: Improvement > Components: core > Versions: 3.1 beta 1 > Reporter: Alexey Kaigorodov > Priority: Minor > > > Please add support querying against values in a collection of values in the Criteria API. > Related links: > http://forum.hibernate.org/viewtopic.php?t=932908 > http://forum.hibernate.org/viewtopic.php?t=943792 > http://forum.hibernate.org/viewtopic.php?t=946236 > Best regards, > Alexey -- 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

17 years, 7 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-869) Querying collections of value type in the Criteria API

by Mattias Jiderhamn (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-869?page=co... ] Mattias Jiderhamn commented on HHH-869: --------------------------------------- On the other hand, this is an *exception* to something Hibernate *can* do. Hibernate can query collections using the Criteria API and Hibernate supports value collections. If Hibernate could create gravity, and could create anti-materia (or anti-whatever), I might expect a disclaimer about not being able to create anti-gravity... ;-) > Querying collections of value type in the Criteria API > ------------------------------------------------------ > > Key: HHH-869 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-869 > Project: Hibernate3 > Type: Improvement > Components: core > Versions: 3.1 beta 1 > Reporter: Alexey Kaigorodov > Priority: Minor > > > Please add support querying against values in a collection of values in the Criteria API. > Related links: > http://forum.hibernate.org/viewtopic.php?t=932908 > http://forum.hibernate.org/viewtopic.php?t=943792 > http://forum.hibernate.org/viewtopic.php?t=946236 > Best regards, > Alexey -- 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

17 years, 7 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-869) Querying collections of value type in the Criteria API

by Emmanuel Bernard (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-869?page=co... ] Emmanuel Bernard commented on HHH-869: -------------------------------------- Our pattern is to describe what can be done, not the other way around: - because that can change and forgetting about one line in the doc is easy - the number of things not doable exceed the number of things doable ( Hibernate cannot create antigravity ;-) ) > Querying collections of value type in the Criteria API > ------------------------------------------------------ > > Key: HHH-869 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-869 > Project: Hibernate3 > Type: Improvement > Components: core > Versions: 3.1 beta 1 > Reporter: Alexey Kaigorodov > Priority: Minor > > > Please add support querying against values in a collection of values in the Criteria API. > Related links: > http://forum.hibernate.org/viewtopic.php?t=932908 > http://forum.hibernate.org/viewtopic.php?t=943792 > http://forum.hibernate.org/viewtopic.php?t=946236 > Best regards, > Alexey -- 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

17 years, 7 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-869) Querying collections of value type in the Criteria API

by y360 (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-869?page=co... ] y360 commented on HHH-869: -------------------------- This limitation should be documented in a bold and prominent way. As far as I can tell, it is not mentioned explictly in the documentation nor in the "hibernate in action" book. > Querying collections of value type in the Criteria API > ------------------------------------------------------ > > Key: HHH-869 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-869 > Project: Hibernate3 > Type: Improvement > Components: core > Versions: 3.1 beta 1 > Reporter: Alexey Kaigorodov > Priority: Minor > > > Please add support querying against values in a collection of values in the Criteria API. > Related links: > http://forum.hibernate.org/viewtopic.php?t=932908 > http://forum.hibernate.org/viewtopic.php?t=943792 > http://forum.hibernate.org/viewtopic.php?t=946236 > Best regards, > Alexey -- 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

17 years, 7 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HBX-810) Remove redundant generation of @Column default values in annotation codegen

by Max Rydahl Andersen (JIRA)

Remove redundant generation of @Column default values in annotation codegen --------------------------------------------------------------------------- Key: HBX-810 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-810 Project: Hibernate Tools Type: Improvement Components: hbm2java Versions: 3.2beta8 Reporter: Max Rydahl Andersen @Column generates to many defaults. -- 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

17 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues November 2006