October 2009 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Commented: (HHH-1582) PostInsertListener + "post-commit-insert"

by Holger Wagner (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1582?page=c... ] Holger Wagner commented on HHH-1582: ------------------------------------ Here is an stack-trace for this situation: EntityInsertAction.postCommitInsert() line: 126 EntityInsertAction.afterTransactionCompletion(boolean) line: 162 ActionQueue.afterTransactionCompletion(boolean) line: 170 SessionImpl.afterTransactionCompletion(boolean, Transaction) line: 419 JDBCContext.afterTransactionCompletion(boolean, Transaction) line: 209 JDBCTransaction.rollback() line: 174 HibernateTransactionManager.doRollback(DefaultTransactionStatus) line: 603 HibernateTransactionManager(AbstractPlatformTransactionManager).processRollback(DefaultTransactionStatus) line: 583 HibernateTransactionManager(AbstractPlatformTransactionManager).rollback(TransactionStatus) line: 560 AbschnittDao(RevisionDao<T>).runInTransaction(Runnable) line: 622 AbschnittDao(RevisionDao<T>).update(T) line: 571 > PostInsertListener + "post-commit-insert" > ----------------------------------------- > > Key: HHH-1582 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1582 > Project: Hibernate Core > Issue Type: Bug > Affects Versions: 3.1.2 > Reporter: Daniel Gredler > Assignee: Emmanuel Bernard > Original Estimate: 3 hours > Remaining Estimate: 3 hours > > I'm using a custom PostInsertEventListener mapped to the "post-commit-insert" event to process domain objects. However, PostInsertEventListener's onPostInsert(PostInsertEvent) is getting called even when the insert was not successful (ie, due to a unique constraint in the database or some such). It looks to me like Hibernate should either a) not invoke the event listener if the insert failed or b) provide state (perhaps in the form of a boolean indicating success/failure). Personally I'd rather the method not be called on failure, but there may be use cases out there for the second option. > As an example, it looks like Hibernate's own LuceneEventListener will add a domain object to the index in onPostInsert(PostInsertEvent) even if the insert failed. > Note that this problem also seems to exist in EntityDeleteAction and EntityUpdateAction (which would mean that Hibernate's LuceneEventListener removes domain objects from the Lucene index even if the delete fails!). -- 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, 2 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-4513) AnotationConfiguration does not honor hibernate.validator.apply_to_ddl property in case Hibernate Validator 4 is activated

by Hardy Ferentschik (JIRA)

AnotationConfiguration does not honor hibernate.validator.apply_to_ddl property in case Hibernate Validator 4 is activated -------------------------------------------------------------------------------------------------------------------------- Key: HHH-4513 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4513 Project: Hibernate Core Issue Type: Bug Components: annotations Affects Versions: 3.5.0.Beta-1 Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik Fix For: 3.5 -- 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, 2 months

1
1
0 / 0

[Hibernate-JIRA] Commented: (HHH-1268) Unidirection OneToMany causes duplicate key entry violation when removing from list

by Loïc Lefèvre (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1268?page=c... ] Loïc Lefèvre commented on HHH-1268: ----------------------------------- Hello, any news about the resolution of this issue? > Unidirection OneToMany causes duplicate key entry violation when removing from list > ----------------------------------------------------------------------------------- > > Key: HHH-1268 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1268 > Project: Hibernate Core > Issue Type: Bug > Affects Versions: 3.1 > Environment: 3.1 final > MySql 4.1.14 using MYISAM tables > Reporter: Rex Madden > Assignee: Gail Badner > Fix For: 3.2.x, 3.3.x > > Attachments: src.zip > > > Simple OneToMany parent/child relationship using the default table structure (2 tables and a join table) > Add 3 children to the parent. Flush. Remove the first child. Flush throws error: > Exception in thread "main" org.hibernate.exception.ConstraintViolationException: Could not execute JDBC batch update > at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:69) > at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43) > at org.hibernate.jdbc.AbstractBatcher.executeBatch(AbstractBatcher.java:202) > at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:230) > at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:143) > at org.hibernate.event.def.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:296) > at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:27) > at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:980) > at UnidirectionalOneToManyRemoveFromListBug.main(UnidirectionalOneToManyRemoveFromListBug.java:27) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at com.intellij.rt.execution.application.AppMain.main(AppMain.java:86) > Caused by: java.sql.BatchUpdateException: Duplicate key or integrity constraint violation, message from server: "Duplicate entry '5' for key 2" > at com.mysql.jdbc.PreparedStatement.executeBatch(PreparedStatement.java:1461) > at org.hibernate.jdbc.BatchingBatcher.doExecuteBatch(BatchingBatcher.java:58) > at org.hibernate.jdbc.AbstractBatcher.executeBatch(AbstractBatcher.java:195) > ... 11 more > The problem is that there is a unique key on the relationship table that gets violated. The session removes the last row in the relationship table, then attempts to rewrite the child_id's. It fails since there is a uniqueness constraint on that column. -- 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, 2 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-4514) ClassCastException at runtime

by Amit (JIRA)

ClassCastException at runtime ----------------------------- Key: HHH-4514 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4514 Project: Hibernate Core Issue Type: Bug Components: query-hql Affects Versions: 3.2.7 Environment: development Reporter: Amit Attachments: HibernatePPHQDAO.java I have read in the migration guide regarding the changes but not sure how to incorporate following into my existing code. Configuration classicCfg = new Configuration(); classicCfg.addSqlFunction( "count", new ClassicCountFunction()); classicCfg.addSqlFunction( "avg", new ClassicAvgFunction()); classicCfg.addSqlFunction( "sum", new ClassicSumFunction()); SessionFactory classicSf = classicCfg.buildSessionFactory(); -- 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, 2 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-4473) Create documentation to explain the usage of the new 'defaultForType' attribute of the TypeDef annotation

by Sharath Reddy (JIRA)

Create documentation to explain the usage of the new 'defaultForType' attribute of the TypeDef annotation ---------------------------------------------------------------------------------------------------------- Key: HHH-4473 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4473 Project: Hibernate Core Issue Type: New Feature Components: annotations Reporter: Sharath Reddy -- 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, 2 months

1
2
0 / 0

[Hibernate-JIRA] Created: (HBX-1150) hibernate.hbm2ddl.auto update option is enforcing a foreign key constraint for many-to-one mapping with not-found="ignore"

by Rani (JIRA)

hibernate.hbm2ddl.auto update option is enforcing a foreign key constraint for many-to-one mapping with not-found="ignore" -------------------------------------------------------------------------------------------------------------------------- Key: HBX-1150 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-1150 Project: Hibernate Tools Issue Type: Bug Affects Versions: 3.2.cr1 Environment: windows , hsqldb Reporter: Rani hi, i am using dbunit with hibernate for configuring datasets for test cases. As part of the test case/suite setup we configure the hsql in memory db and setup the database. We have used hibernate.hbm2ddl.auto update. I have few hbm's with many-to-one mappings with the attribute not-found="ignore" . Looks like the the above setting of hbm2ddl to update is enforcing FK constraint. Defining the FK constraint for just many-to-one should be okay, but it should not be enforced if the many-to-one mapping has the attribute not-found="ignore". The actual database in production does not have any FK constraint. Appreciate if we could get a fix or workaround for the same. -- 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, 2 months

2
3
0 / 0

[Hibernate-JIRA] Commented: (HHH-1582) PostInsertListener + "post-commit-insert"

by Holger Wagner (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1582?page=c... ] Holger Wagner commented on HHH-1582: ------------------------------------ I've tried the 3.3.2-Version and got the same behavior - so I checked the 'bad'-call coming from the rollback-method by adding a transient flag to my objects. When you will really fix this problem? > PostInsertListener + "post-commit-insert" > ----------------------------------------- > > Key: HHH-1582 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1582 > Project: Hibernate Core > Issue Type: Bug > Affects Versions: 3.1.2 > Reporter: Daniel Gredler > Assignee: Emmanuel Bernard > Original Estimate: 3 hours > Remaining Estimate: 3 hours > > I'm using a custom PostInsertEventListener mapped to the "post-commit-insert" event to process domain objects. However, PostInsertEventListener's onPostInsert(PostInsertEvent) is getting called even when the insert was not successful (ie, due to a unique constraint in the database or some such). It looks to me like Hibernate should either a) not invoke the event listener if the insert failed or b) provide state (perhaps in the form of a boolean indicating success/failure). Personally I'd rather the method not be called on failure, but there may be use cases out there for the second option. > As an example, it looks like Hibernate's own LuceneEventListener will add a domain object to the index in onPostInsert(PostInsertEvent) even if the insert failed. > Note that this problem also seems to exist in EntityDeleteAction and EntityUpdateAction (which would mean that Hibernate's LuceneEventListener removes domain objects from the Lucene index even if the delete fails!). -- 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, 2 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-3919) Hibernate uses DROP TABLE to drop temporary tables - it should use DROP TEMPORARY TABLE

by Donnchadh O Donnabhain (JIRA)

Hibernate uses DROP TABLE to drop temporary tables - it should use DROP TEMPORARY TABLE --------------------------------------------------------------------------------------- Key: HHH-3919 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3919 Project: Hibernate Core Issue Type: Bug Components: query-hql Affects Versions: 3.3.1 Environment: MySQL 5.0.77 Reporter: Donnchadh O Donnabhain DROP TABLE requires DROP TABLE permission whereas DROP TEMPORARY TABLE doesn't. Currently the drop command is hardcoded as "drop table " in AbstractStatementExecutor.java (line 177). Something like getFactory().getDialect().getDropTemporaryTableString() is needed. -- 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, 2 months

4
6
0 / 0

[Hibernate-JIRA] Created: (HHH-4512) TypeDef annotation should support both 'name' and 'defaultForType' attributes

by Sharath Reddy (JIRA)

TypeDef annotation should support both 'name' and 'defaultForType' attributes ----------------------------------------------------------------------------- Key: HHH-4512 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4512 Project: Hibernate Core Issue Type: New Feature Components: annotations Reporter: Sharath Reddy Assignee: Sharath Reddy Priority: Minor Fix For: 3.5 Currently only one or the other attribute is supported. -- 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, 2 months

1
1
0 / 0

[Hibernate-JIRA] Created: (ANN-794) Polymorphic query on abstract function

by radu (JIRA)

Polymorphic query on abstract function -------------------------------------- Key: ANN-794 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-794 Project: Hibernate Annotations Issue Type: Bug Affects Versions: 3.3.0.ga Reporter: radu Priority: Blocker I have the following classes adnnotated with hibernate: <pre><code> @Entity @Inheritance(strategy=InheritanceType.JOINED) public abstract class Symbol implements Serializable { @Id @GeneratedValue(strategy = GenerationType.AUTO) private Integer id; @AccessType("property") public abstract String getCode(); @AccessType("property") public abstract void setCode(String code); } @javax.persistence.Entity @AttributeOverride( name="code", column = @Column(name="field1") ) public class Child1 extends Symbol { @Basic @Column(nullable = false) private String field1; @AccessType("property") public String getCode() { return getField1(); } @AccessType("property") public void setCode(String code) { setField1(code); } public void setField1(String field1) { this.field1 = field1; } public String getField1() { return field1; } } @javax.persistence.Entity @AttributeOverride( name="code", column = @Column(name="field2") ) public class Child2 extends Symbol { @Basic @Column(nullable = false) private String field2; @AccessType("property") public String getCode() { return getField2(); } @AccessType("property") public void setCode(String code) { setField1(code); } public void setField1(String field2) { this.field2 = field2; } public String getField2() { return field2; } } </code></pre> As objectual rules about polymorphisms the following query should be valid and to retrieve correct field value: session.createQuery("from Symbol s where s.code = :code"); but it give me the error: org.hibernate.QueryException: could not resolve property: code of: ... Please give some advices how to work around this problem if this situation does not follow hibernate concept or JPA specs and is not possible to implement it. Idea is that it should be possible to work at hight level without changing database or existing classes. Thanks -- 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, 2 months

4
5
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues October 2009