February 2009 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-3791) Primary Key class (@IdClass) used as object values and implies foreign key

by Timothy Twelves (JIRA)

Primary Key class (@IdClass) used as object values and implies foreign key -------------------------------------------------------------------------- Key: HHH-3791 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3791 Project: Hibernate Core Issue Type: Improvement Components: core, metamodel, query-hql Reporter: Timothy Twelves As per: http://forums.hibernate.org/viewtopic.php?t=991417 Map primary key objects enforcing referential integrity without mapping the actual object. This ensures that there is no possibility for lazy loading and also becomes nice for serialization and data transport. {code:title=MyExample.java|borderStyle=solid} @Entity @IdClass(AccountPk.class) class Account { long accountNo; PersonPk owner; // <---- here we refer many to one but using PersonPk instead of Person } class AccountPk { long accountNo; } class PersonPk { int person; } @Entity @IdClass(PersonPk.class) class Person { int id; AccountPk primaryAccount; Collection<AccountPk> accounts; // <---- here we have one to many but using AccountPk instead of Account } {code} The above example is insufficient as the PK object does not indicate its entity. @PrimaryEntity and @PrimaryEntityCollection is used below as an example how this would be marked appropriately. {code:title=MyExample.java|borderStyle=solid} @Entity @IdClass(AccountPk.class) class Account { long accountNo; @PrimaryEntity(entity=Person.class) PersonPk owner; } class AccountPk { long accountNo; } class PersonPk { int person; } @Entity @IdClass(PersonPk.class) class Person { int id; AccountPk primaryAccount; @PrimaryEntityCollection(entity=Person.class, primarykey=AccountPk.class) Collection<AccountPk> accounts; } {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

17 years, 1 month

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-3790) add java.util.EventListener marker interface so that hibernate event listeners can be used by the java beans introspector code

by Patrick Moore (JIRA)

add java.util.EventListener marker interface so that hibernate event listeners can be used by the java beans introspector code ------------------------------------------------------------------------------------------------------------------------------ Key: HHH-3790 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3790 Project: Hibernate Core Issue Type: Patch Affects Versions: 3.5 Reporter: Patrick Moore Attachments: patch.txt I am using a Dependency Injection framework. I have classes that extend the org.hibernate.events.*EventListener interfaces. I would like my implementations injected as eventlisteners by the DI framework. The DI framework is using the java.beans.Introspector code. The java.util.EventListener interface is required by the java.beans. java.util.EventListener adds no additional methods. -- 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

1
0
0 / 0

[Hibernate-JIRA] Created: (BVAL-131) Provide object graph determinism

by Emmanuel Bernard (JIRA)

Provide object graph determinism -------------------------------- Key: BVAL-131 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-131 Project: Bean Validation Issue Type: Improvement Components: spec-general Affects Versions: 1.0 public draft Reporter: Emmanuel Bernard Fix For: 1.0 proposed final draft -- 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

1
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3780) DB2 materialized views are not retrieved in DatabaseMetadata

by Julien Kronegg (JIRA)

DB2 materialized views are not retrieved in DatabaseMetadata ------------------------------------------------------------ Key: HHH-3780 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3780 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.1 Environment: Hibernate 3.3.1.GA Reporter: Julien Kronegg Priority: Minor The class org.hibernate.tool.hbm2ddl.DatabaseMetadata.getTableMetadata() gets the table with the specified name and restricts the type to either "TABLE" or "VIEW" (see TYPES constant). Consequently, DB2 materialized view tables cannot be retrieved because their type is "MATERIALIZED QUERY TABLE", i.e. neither "TABLE" nor "VIEW". Note: for a full list of DB2 types, see http://publib.boulder.ibm.com/infocenter/iseries/v5r4/index.jsp?topic=/cl... or use the following code snippet: Connection con = ... // a connection to a DB2 database ResultSet rs = con.getMetaData().getTableTypes(); while (rs.next()) { System.out.println(rs.getObject(1)); } A similar problem occured for views before: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1329 Two solutions: 1) add "MATERIALIZED QUERY TABLE" in the org.hibernate.tool.hbm2ddl.DatabaseMetadata.TYPES constant. 2) change Hibernate FAQ by http://www.hibernate.org/116.html#A28 by adding a note about materialized views under DB2 Solution (1) would be better IMHO. Workaround: since the hibernate tools cannot get the table structure from the metadata (e.g. when using seam-gen), it is required to write the mapping file by hand. -- 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

1
4
0 / 0

[Hibernate-JIRA] Created: (HHH-3786) using System.out instead of Logger

by Macko Usko (JIRA)

using System.out instead of Logger ---------------------------------- Key: HHH-3786 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3786 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.2.4.sp1 Reporter: Macko Usko Priority: Trivial AbstractBatcher class line:404 System.out.println("Hibernate: " + format(sql)); if <property name="hibernate.show_sql" value="true" /> then console log is polluted with System.out.println() logs. Logger should be used instead -- 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

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-3783) Save throws unique constraint violation: Object having a composite-key with constraint on one of the columns

by Soorjith Kombilath (JIRA)

Save throws unique constraint violation: Object having a composite-key with constraint on one of the columns ------------------------------------------------------------------------------------------------------------ Key: HHH-3783 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3783 Project: Hibernate Core Issue Type: Bug Environment: HIbernate 3.2.5.ga; Database: Oracle Reporter: Soorjith Kombilath I have a hibernate object with composite key - <composite-id> <key-many-to-one name="parent" column="PARENT_NUMBER" class="com.test.entity.impl.ParentImpl" /> <key-property name="restraintCode" column="RESTRAINT_CDE" type="string" /> </composite-id> In database there is a unique index on PARENT_NUMBER. Parent object may contain a collection of chjld objects. Whenever a child object is removed and a new child object is added, it throws unique constraint violation error. When I check the queries generated, hibernate is executing the queries for INSERT before executing DELETE. Is there any way to enforce DELETE before INSERTS? or am I missing to specify some attribute in my mapping? -- 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
3
0 / 0

[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: (BVAL-129) Clarify ConstraintValidatorContext propertyPath generation

by Emmanuel Bernard (JIRA)

Clarify ConstraintValidatorContext propertyPath generation ---------------------------------------------------------- Key: BVAL-129 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-129 Project: Bean Validation Issue Type: Improvement Components: spec-general Affects Versions: 1.0 public draft Reporter: Emmanuel Bernard Fix For: 1.0 proposed final draft -- 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

1
1
0 / 0

[Hibernate-JIRA] Created: (BVAL-55) Exception policy

by Emmanuel Bernard (JIRA)

Exception policy ---------------- Key: BVAL-55 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-55 Project: Bean Validation Issue Type: New Feature Components: spec-general 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

17 years, 1 month

1
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 February 2009