August 2008 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-2792) Session.delete is validate all fields are null

by Daniel Passos (JIRA)

Session.delete is validate all fields are null ---------------------------------------------- Key: HHH-2792 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2792 Project: Hibernate3 Issue Type: Bug Components: core Reporter: Daniel Passos session.delete operation would not have to validate if the fields are null The problem in DefaultDeleteEventListener.deleteEntity -> Nullability.checkNullability -- 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, 1 month

6
5
0 / 0

[Hibernate-JIRA] Created: (HHH-2801) wrong insert/delete order when updating record-set

by Christoph Mayerhofer (JIRA)

wrong insert/delete order when updating record-set -------------------------------------------------- Key: HHH-2801 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2801 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.4.sp1 Environment: hibernate-3.2.4.sp1, hibernate-annotations-3.3.0.GA, hibernate-entitymanager-3.3.1.GA, Oracle 10g Express Edition Reporter: Christoph Mayerhofer Attachments: model.zip Overview: I have a record with a OneToMany association. From this associated record-set a record is removed and added again, both records identified with the same key. When doing a merge, I get a Unique constraint violation, because Hibernate first tries to insert the new record. Hibernate should first delete the old record, and after this insert the new record, avoiding the unique constraint violation. Detailed description: I have the following entities: Patient, SocialInsurance, PatientSocialInsurance. A patient could have several social insurances assigned to it. A social insurance could be assigned several times to a patient, we have a m:n relation between Patient and SocialInsurance. The relation-table has the name PatientSocialInsurance, with a unique constraint over patient_id and social_insurance_id. Each POJO inherits from a Base-POJO, which holds the id and the insert- and update-timestamps and userstamps. Base ---> PatientEntity ---> Patient Base ---> SocialInsuranceEntity ---> SocialInsurance Base ---> PatientSocialInsuranceEntity ---> PatientSocialInsurance Note: All *Entity model objects are generated with Hibernate-Tools from the db-schema, assuming that there are no wrong annotations, no wrong fields or wrong getter-/setter-methods in these model-classes. (I have enclosed all model-classes within an zipped attachment.) Now I try to delete an existing social insurance from a patient and add the same social insurance to the patient again: public void deleteSocialInsurance(Patient p, PatientSocialInsurance s) { if (p == null || s == null) { throw new IllegalArgumentException(); } s.setSocialInsurance(null); s.setPatient(null); p.getPatientSocialInsurances().remove(s); } public void addPatientSocialInsurance(Patient p, PatientSocialInsurance s) throws DuplicatePatientSocInsException { if (p == null || s == null) { throw new IllegalArgumentException(); } s.setPatient(p); p.getPatientSocialInsurances().add(s); } After doing a merge on the patient object, I get the following error: DEBUG - persisting patient... DEBUG - transaction org.hibernate.ejb.TransactionImpl@44ac6a started DEBUG - update timestamp and userstamp for base record set DEBUG - update timestamp and userstamp for base record set DEBUG - update timestamp and userstamp for base record set DEBUG - update timestamp and userstamp for base record set DEBUG - update timestamp and userstamp for base record set DEBUG - select rawtohex(sys_guid()) from dual DEBUG - insert timestamp and userstamp for base record set DEBUG - insert into dseas.PATIENT_SOCIAL_INSURANCE (TIME_CRE, TIME_UPD, USER_CRE, USER_UPD, CODE_MEMBERSHIP_NO, CODE_TYPE_DEFAULT, PATIENT_ID, SOC_INS_ID, ID) values (?, ?, ?, ?, ?, ?, ?, ?, ?) ERROR - ORA-00001: Unique Constraint (DSEAS.PATIENT_SOCIAL_INSURANCE_UK) verletzt ERROR - ORA-00001: Unique Constraint (DSEAS.PATIENT_SOCIAL_INSURANCE_UK) verletzt ERROR - Could not synchronize database state with session org.hibernate.exception.ConstraintViolationException: Could not execute JDBC batch update at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:71) at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43) at org.hibernate.jdbc.AbstractBatcher.executeBatch(AbstractBatcher.java:253) at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:237) at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:141) at org.hibernate.event.def.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:298) at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:27) at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:1000) at org.hibernate.impl.SessionImpl.managedFlush(SessionImpl.java:338) at org.hibernate.transaction.JDBCTransaction.commit(JDBCTransaction.java:106) at org.hibernate.ejb.TransactionImpl.commit(TransactionImpl.java:54) at org.dseas.base.hibernate.EntityManagerFacade.commit(EntityManagerFacade.java:78) at org.dseas.business.service.maindata.PatientEditorService.save(PatientEditorService.java:112) at org.dseas.ui.rcp.editor.patient.PatientEditorPart.doSave(PatientEditorPart.java:1298) at org.eclipse.ui.internal.SaveableHelper$1.run(SaveableHelper.java:143) at org.eclipse.ui.internal.SaveableHelper$4.run(SaveableHelper.java:266) at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:369) at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:313) at org.eclipse.jface.window.ApplicationWindow$1.run(ApplicationWindow.java:758) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:67) at org.eclipse.jface.window.ApplicationWindow.run(ApplicationWindow.java:755) at org.eclipse.ui.internal.WorkbenchWindow.run(WorkbenchWindow.java:2451) at org.eclipse.ui.internal.SaveableHelper.runProgressMonitorOperation(SaveableHelper.java:274) at org.eclipse.ui.internal.SaveableHelper.runProgressMonitorOperation(SaveableHelper.java:253) at org.eclipse.ui.internal.SaveableHelper.savePart(SaveableHelper.java:148) at org.eclipse.ui.internal.EditorManager.savePart(EditorManager.java:1345) at org.eclipse.ui.internal.WorkbenchPage.savePart(WorkbenchPage.java:3184) at org.eclipse.ui.internal.WorkbenchPage.saveEditor(WorkbenchPage.java:3197) at org.eclipse.ui.internal.SaveAction.run(SaveAction.java:73) at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:545) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:490) at org.eclipse.jface.action.ActionContributionItem$6.handleEvent(ActionContributionItem.java:443) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:938) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3682) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3293) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2389) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219) at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:461) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.dseas.ui.rcp.Application.start(Application.java:22) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:153) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:363) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:504) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:443) at org.eclipse.equinox.launcher.Main.run(Main.java:1169) at org.eclipse.equinox.launcher.Main.main(Main.java:1144) Caused by: java.sql.BatchUpdateException: ORA-00001: Unique Constraint (DSEAS.PATIENT_SOCIAL_INSURANCE_UK) verletzt at oracle.jdbc.driver.DatabaseError.throwBatchUpdateException(DatabaseError.java:343) at oracle.jdbc.driver.OraclePreparedStatement.executeBatch(OraclePreparedStatement.java:10657) at org.hibernate.jdbc.BatchingBatcher.doExecuteBatch(BatchingBatcher.java:48) at org.hibernate.jdbc.AbstractBatcher.executeBatch(AbstractBatcher.java:246) ... 55 more ERROR - Error while commiting the transaction -- 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, 1 month

10
21
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-234) add to maven repository (not jboss).

by chun ping wang (JIRA)

add to maven repository (not jboss). ------------------------------------- Key: HSEARCH-234 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-234 Project: Hibernate Search Issue Type: Improvement Reporter: chun ping wang is it possible to copy the jboss repository and move the dependecy toward main maven 2 repository. I kinda don't want to point to two different repository. -- 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, 1 month

3
4
0 / 0

[Hibernate-JIRA] Created: (HBX-893) "Can't create session factory" if any @NamedQuery annotations on entities have errors in them

by Joseph Marques (JIRA)

"Can't create session factory" if any @NamedQuery annotations on entities have errors in them --------------------------------------------------------------------------------------------- Key: HBX-893 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-893 Project: Hibernate Tools Type: Bug Versions: 3.2beta8 Reporter: Joseph Marques This seems to be a pretty big restriction - especially if you want to be able to cater to those that try to adopt Hibernate Tools part of the way through development, where some annotations may already have errors in them. Instead, it should be much more user-friendly to expand the session factory anyway, but just not load those entities - perhaps even marking them with a little red 'X' to indicate that the user needs to fix something in them. -- 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, 1 month

2
5
0 / 0

[Hibernate-JIRA] Created: (HBX-1047) Constructor uses the non generated properties even though Meta tag attribute="gen-property" value is set to "false".

by Sukirtha Joseph (JIRA)

Constructor uses the non generated properties even though Meta tag attribute="gen-property" value is set to "false". --------------------------------------------------------------------------------------------------------------------- Key: HBX-1047 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-1047 Project: Hibernate Tools Issue Type: Bug Components: hbm2java Environment: Hibernate 3.0 Reporter: Sukirtha Joseph Constructor uses the non generated properties even though Meta tag attribute="gen-property" value is set to "false". Thus class compilation 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

17 years, 1 month

3
10
0 / 0

[Hibernate-JIRA] Created: (ANN-597) @Index doesn't create multi-column indexes

by Christian Bauer (JIRA)

@Index doesn't create multi-column indexes ------------------------------------------ Key: ANN-597 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-597 Project: Hibernate Annotations Issue Type: Bug Components: binder Affects Versions: 3.3.0.ga Reporter: Christian Bauer Priority: Minor @org.hibernate.annotations.Index(name = "IDX_COMPONENT_PROPERTY_NAME", columnNames = {"COMPONENT_NAME", "PROPERTY_NAME"}) create index IDX_COMPONENT_PROPERTY_NAME on PREFERENCE (PROPERTY_NAME); -- 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, 1 month

3
3
0 / 0

[Hibernate-JIRA] Created: (HBX-1053) [PATCH] In Hbm2DDLExporterTask report errors if schemaUpdate = true

by Johannes Rudolph (JIRA)

[PATCH] In Hbm2DDLExporterTask report errors if schemaUpdate = true ------------------------------------------------------------------- Key: HBX-1053 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-1053 Project: Hibernate Tools Issue Type: Patch Components: ant Affects Versions: 3.2.1 Reporter: Johannes Rudolph Attachments: better_exception_reporting.patch The current hbm2ddl doesn't report any errors if schemaUpdate=true. This may be that the SQL Driver cannot be found or any errors when exporting the generated script to DB. I attached a patch to fix it by reusing the error reporting code use if schemaUpdate=false. -- 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, 1 month

3
5
0 / 0

[Hibernate-JIRA] Created: (HBX-757) Add output file name, delimiter, halt on error, and format options to SchemaUpdate/<hbm2ddl>

by Dan Ports (JIRA)

Add output file name, delimiter, halt on error, and format options to SchemaUpdate/<hbm2ddl> -------------------------------------------------------------------------------------------- Key: HBX-757 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-757 Project: Hibernate Tools Type: Improvement Components: ant Versions: 3.2beta7 Reporter: Dan Ports Priority: Minor The file name, delimiter, halt on error, and format options are provided by SchemaExport/<hbm2ddl> already, so it makes sense to add their functionality to SchemaUpdate as well. I'll submit a patch shortly. (Is this the right place to post this, since SchemaUpdate is in the Hibernate core SVN?) -- 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, 1 month

3
17
0 / 0

[Hibernate-JIRA] Created: (EJB-362) JPA Max/Min aggregate functions do not return same state-field type when argument is a java.sql.Timestamp

by josef (JIRA)

JPA Max/Min aggregate functions do not return same state-field type when argument is a java.sql.Timestamp --------------------------------------------------------------------------------------------------------- Key: EJB-362 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-362 Project: Hibernate Entity Manager Issue Type: Bug Components: EntityManager Affects Versions: 3.3.2.GA Environment: JDK 1.6, Postgres 8.2, JDBC 4 Reporter: josef According the JPQL specification, MAX and MIN aggregate functions should return the type of the state-field to which they are applied. However, if one tries to query MAX or MIN on a java.sql.Timestamp entity field and tries to populate a class which expects a java.sql.Timestamp in the constructor with the result of MAX or MIN, Hibernate fails with javax.persistence.PersistenceException. The result of MAX or MIN in this case are being java.util.Date instead. The error result in type mismatch should ideally also be more helpful, because it is very difficult to understand what and where the problem is, unless you know about it beforehand. Here is an example Entity, with the aggregate class and query, together with the exception that occurs: ... import java.sql.Timestamp; @Entity @Table(name="pending_events") public class PendingEvent implements Serializable { ... @Column(name="event_time", updatable=false, nullable=false) private Timestamp eventTime; ... } import java.sql.Timestamp; public class EventEntry { private String sender; private Timestamp lastEventTime; public EventEntry(String sender, Timestamp lastEventTime) { this.sender= sender; this.lastEventTime = lastEventTime; } ... } SELECT NEW mt.com.jbx.EventEntry(p.sender, MAX(p.eventTime)) FROM PendingEvent p WHERE p.recipient.id=? GROUP BY p.sender ORDER BY MAX(p.eventTime) DESC java.lang.ExceptionInInitializerError Caused by: javax.persistence.PersistenceException: [PersistenceUnit: EventsPU] Unable to build EntityManagerFactory at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:677) at org.hibernate.ejb.HibernatePersistence.createEntityManagerFactory(HibernatePersistence.java:126) at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:52) at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:34) at mt.com.jbx.EventHandler.<clinit>(EventHandler.java:33) Caused by: org.hibernate.HibernateException: Errors in named queries: getEventSummary at org.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:365) at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1300) at org.hibernate.cfg.AnnotationConfiguration.buildSessionFactory(AnnotationConfiguration.java:859) at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:669) -- 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, 2 months

5
11
0 / 0

[Hibernate-JIRA] Created: (HHH-3427) executeUpdate never completes

by Mojmir Tuljak (JIRA)

executeUpdate never completes ----------------------------- Key: HHH-3427 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3427 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.2.0.ga Environment: Hibernate 3.2.0 ga, Oracle 10.2.0.1.0, JAVA 1.6 Reporter: Mojmir Tuljak Update (query.executeUpdate()) never completes. Using oracle enterprise manager we can see that oracle has completed the update but method executedUpdate() never returned any result so the application is waiting. The problem is not always reproducable and happens once or twice a day, always when the same executeUpdate is called while the previous one is still in progress. No exception is thrown. Executing the same query directly without the use of hibernate does not lead to the above problems. -- 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, 2 months

3
2
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 August 2008