March 2010 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-2608) allow delete-orphan cascade style in one-to-one mapping

by Joe Kelly (JIRA)

allow delete-orphan cascade style in one-to-one mapping ------------------------------------------------------- Key: HHH-2608 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2608 Project: Hibernate3 Issue Type: New Feature Components: core Affects Versions: 3.2.4 Environment: 3.2.4, DB2 v8 Reporter: Joe Kelly Please allow the cascade-style "delete-orphan" for one-to-one relationships. When I try to use that cascade style, I get the exception "org.hibernate.MappingException: single-valued associations do not support orphan delete". I realize that the reference manual says "Note that single valued associations (many-to-one and one-to-one associations) do not support orphan delete." But why? I can think of many cases where you WOULD want parent-child semantics in a one-to-one relationship. For example, I have encountered some legacy databases where an entity has all of its fields stored in one table EXCEPT for an optional large field (e.g. a blob field) that is stored in another table, presumably for some performance or storage optimization reason. In this case the two tables are joined with a one-to-one relationship, using a shared primary key. Here are some hypothetical tables, classes and mappings that illustrate this example: company ( company_id (PK) name ) company_extra ( company_extra_id (PK), (FK referencing company.company_id) some_extra_info ) class Company { int companyId; String name; CompanyExtra companyExtra; } class CompanyExtra { int companyExtraId; String someExtraInfo; Company company; } <class name="Company" table="company"> <id name="companyId" column="company_id"> <generator class="sequence"> <param name="sequence">COMPANY_SEQ</param> </generator> </id> <property name="name" column="name" /> <one-to-one name="companyExtra" class="CompanyExtra" cascade="all, delete-orphan" /> </class> <class name="CompanyExtra" table="company_extra"> <id name="companyExtraId" column="company_extra_id" unsaved-value="null"> <generator class="foreign"> <param name="property">company</param> </generator> </id> <property name="someExtraInfo" column="some_extra_info" /> <one-to-one name="company" class="Company" constrained="true" /> </class> For the purposes of this example, CompanyExtra is a child of Company and belongs to one and only one instance of Company. It cannot be shared between Company instances and it cannot be an orphan (i.e. it cannot exist without a parent Company). Also, CompanyExtra is optional so you can have a Company without any associated CompanyExtra during Company's lifecycle. To me, it seems natural and logical that if you set Company.companyExtra to null, and save Company, Hibernate should automatically delete the associated record in the company_extra table if the delete-orphan cascade style is configured (which, of course, it not currently allowed). This is what I want to do when editing an existing Company instance: aCompany = session.load(...); aCompany.setCompanyExtra(null); aCompany.setName("some new name"); session.save(aCompany); // automatically deletes company_extra record For now, I think the workaround is to explicitly delete the CompanyExtra instance in Java code but that just doesn't seem natural to me and it isn't transparent. I do NOT want to do this: aCompany = session.load(...); companyExtra = aCompany.getCompanyExtra(); // ***extra, unnatural method call aCompany.setCompanyExtra(null); aCompany.setName("some new name"); session.save(aCompany); session.delete(companyExtra); // ***another extra, unnatural method call -- 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, 9 months

17
20
0 / 0

[Hibernate-JIRA] Created: (ANN-573) Many-to-many with Attributes (Attribute-class with two @ManyToOne mappings as @Id) not possible

by Christian Köberl (JIRA)

Many-to-many with Attributes (Attribute-class with two @ManyToOne mappings as @Id) not possible ----------------------------------------------------------------------------------------------- Key: ANN-573 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-573 Project: Hibernate Annotations Type: Bug Components: binder Versions: 3.2.1 Environment: Hibernate+Annotations 3.2.1-ga, HSQLDB 1.8.0.7 Reporter: Christian Köberl Attachments: manytomanybug.zip Im trying to map the following relation: Order 1-n OrderLine m-1 Product where the OrderLine contains an amount of the ordered product. The problem seems to be multiple @Id in combination with @ManyToOne: @Entity @Table(name = "order_line") // @IdClass(OrderLinePK.class) public class OrderLine implements Serializable { @Id @ManyToOne(targetEntity = Order.class) @JoinColumn(name = "order_id", nullable = false) private Order order; @Id @ManyToOne(targetEntity = Product.class) @JoinColumn(name = "product_id", nullable = false) ... } Hibernate maps the OrderLine class in the following way: DEBUG SchemaUpdate:149 - create table order_line (product varbinary(255) not null, order varbinary(255) not null, amount integer, primary key (order)) (maybe this relates to http://opensource.atlassian.com/projects/hibernate/browse/ANN-435) When I add an IdClass to the OrderLine, I get the following exception: Initial SessionFactory creation failed.org.hibernate.AnnotationException: mappedBy reference an unknown target entity property: model.OrderLine.order in model.Order.lineItems The example is attached as a runnable Maven2-Project, just run mvn test. The test dao.OrderDaoAnnotationTest fails. In the project I also tried to map the same classes with hbm-Files and this works (dao.OrderDaoHbmTest). -- 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, 9 months

5
7
0 / 0

[Hibernate-JIRA] Created: (HHH-4744) Incorrect audit entity for TABLE_PER_CLASS with abstract classes (results in query error)

by Volker Schmidt (JIRA)

Incorrect audit entity for TABLE_PER_CLASS with abstract classes (results in query error) ----------------------------------------------------------------------------------------- Key: HHH-4744 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4744 Project: Hibernate Core Issue Type: Bug Components: envers Affects Versions: 3.5.0-Beta-2, 3.2.0.ga Reporter: Volker Schmidt Attachments: envers-1.2.2.ga-hibernate-3.3.patch, trunk.patch The configuration code of Envers does not check the abstract flag of a PersistentClass. Thus the created audit entity is not declared as being abstract. Abstract entities do not have concrete tables. Without declaring the audit entity of a super class as being abstract, queries include a table (that does not exist) for the abstract super class. I have added a patch for the trunk and for Envers 1.2.2. -- 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, 9 months

3
2
0 / 0

[Hibernate-JIRA] Created: (HHH-4078) EntityMetamodel#entityNameByInheritenceClassNameMap mapping from class or class names?

by Tsering Shrestha (JIRA)

EntityMetamodel#entityNameByInheritenceClassNameMap mapping from class or class names? -------------------------------------------------------------------------------------- Key: HHH-4078 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4078 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.5 Reporter: Tsering Shrestha In the constructor of EntityMetaModel (http://anonsvn.jboss.org/repos/hibernate/core/trunk/core/src/main/java/or... revision 15258) Line 314: if ( persistentClass.hasPojoRepresentation() ) { entityNameByInheritenceClassNameMap.put( persistentClass.getMappedClass(), persistentClass.getEntityName() ); However at Line 578: public String findEntityNameByEntityClass(Class inheritenceClass) { return ( String ) entityNameByInheritenceClassNameMap.get( inheritenceClass.getName() ); } Why are we using java.lang.Class as the keys when we put new entries to the map but try to read with java.lang.String keys? -- 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, 9 months

4
5
0 / 0

[Hibernate-JIRA] Created: (HHH-4438) It is impossible to override RelationTargetAuditMode using AuditOverride

by Eugene Goroschenya (JIRA)

It is impossible to override RelationTargetAuditMode using AuditOverride ------------------------------------------------------------------------ Key: HHH-4438 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4438 Project: Hibernate Core Issue Type: Bug Components: envers Affects Versions: 3.5.0.Beta-1, 3.3.2, 3.3.x, 3.5 Reporter: Eugene Goroschenya The implementation of HHH-4010 provides great feature: support auditing of entity having reference (many-to-one relation) to not audited entity But it is still impossible to use it with @Embedded to override RelationTargetAuditMode for some reference(s) in @Embeddable class. -- 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, 9 months

3
3
0 / 0

[Hibernate-JIRA] Created: (HHH-4626) OneToMany cascadeType.ALL change collection and merge - does not remove entities

by Dave (JIRA)

OneToMany cascadeType.ALL change collection and merge - does not remove entities --------------------------------------------------------------------------------- Key: HHH-4626 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4626 Project: Hibernate Core Issue Type: Bug Components: entity-manager Affects Versions: 3.3.1 Environment: JBoss 5.1.0.GA, FC 10, Java 1.6 Reporter: Dave public Class Foo { @OneToMany(fetch=FetchType.LAZY, cascade={CascadeType.ALL}, mappedBy="foo") public List<Bar> getBars() { return bars; } } // aFoo is persited Foo aFoo = ... aFoo.getBars().remove(0); // remove the first aFoo.getBars().add(aBar); // add new one em.merge(aFoo); For cascade={CascadeType.ALL}, it works for creating/deleting aFoo. For merge, the new aBar is created, but the bar that was removed from collection are not deleted from persistence. -- 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, 9 months

3
6
0 / 0

[Hibernate-JIRA] Created: (HHH-3940) Remove hasSelfReferentialForeignKeyBug (returning true) override from MySQL dialects

by Steve Ebersole (JIRA)

Remove hasSelfReferentialForeignKeyBug (returning true) override from MySQL dialects ------------------------------------------------------------------------------------ Key: HHH-3940 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3940 Project: Hibernate Core Issue Type: Task Components: core Affects Versions: 3.3.1, 3.2.7 Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.2.x, 3.3.x, 3.5 Previous versions of MySQL had a nasty bug when using self-referential foreign keys with the innodb storage engine. This Dialect#hasSelfReferentialForeignKeyBug was originally added to account for that. Testing against the lastest (5.1) MySQL versions shows this to no longer be present. -- 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, 9 months

2
7
0 / 0

[Hibernate-JIRA] Created: (HHH-3995) Cleanup test data

by Steve Ebersole (JIRA)

Cleanup test data ----------------- Key: HHH-3995 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3995 Project: Hibernate Core Issue Type: Task Components: testsuite Reporter: Steve Ebersole Assignee: Steve Ebersole Priority: Minor Fix For: 3.2.x, 3.3.x, 3.5 Lots of tests are leaving test data hanging around. That works on a particular assumption wrt the execution order of tests or that only a single test method exists. That cuases problems later in many cases. All tests should clean up the test data they create. Currently on trunk I see 246 tests leaving data around. The sys prop hibernate.test.validateDataCleanup can be used to check for this; set it to true. -- 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, 9 months

2
6
0 / 0

[Hibernate-JIRA] Created: (HHH-2439) delay IDENTITY insertions in the case of FlushMode.MANUAL/NEVER

by Steve Ebersole (JIRA)

delay IDENTITY insertions in the case of FlushMode.MANUAL/NEVER --------------------------------------------------------------- Key: HHH-2439 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2439 Project: Hibernate3 Type: Improvement Components: core Reporter: Steve Ebersole Assigned to: Steve Ebersole Fix For: 3.2.3 Much like we do now in 3.2 for out of transaction operations, we should delay performing insertions for post-insert generators with FlushMode.isManualFlushMode -- 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, 9 months

5
20
0 / 0

[Hibernate-JIRA] Created: (HHH-4706) Leverage new o.h.dialect.function.TrimFunctionTemplate and o.h.dialect.function.AnsiTrimFunction classes

by Steve Ebersole (JIRA)

Leverage new o.h.dialect.function.TrimFunctionTemplate and o.h.dialect.function.AnsiTrimFunction classes -------------------------------------------------------------------------------------------------------- Key: HHH-4706 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4706 Project: Hibernate Core Issue Type: Improvement Components: core, query-hql Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.5 o.h.dialect.function.TrimFunctionTemplate defines basic support for understanding which trim options were specified. o.h.dialect.function.AnsiTrimFunction defines rendering of a trim function using the ANSI SQL defined syntax. -- 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, 9 months

2
5
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 March 2010