[
http://opensource.atlassian.com/projects/hibernate/browse/ANN-682?page=co...
]
Eugene Voytitsky commented on ANN-682:
--------------------------------------
Hah, no, described above workaround doesn't work at all.
I was very optimistic when said that it works -- at time of writing the comment above only
hibernate3-maven-plugin successfully created the SQL script creating the DB schema.
When I try to start my DbUnit tests (which really starts all Hibernate stuff) I got the
error:
Caused by: org.hibernate.MappingException: Duplicate property mapping of user found in
com.foo.bar.Entity1
So my user association "redefinition" actually defines the duplicate.
@ForeignKey override of @MappedSuperclass
-----------------------------------------
Key: ANN-682
URL:
http://opensource.atlassian.com/projects/hibernate/browse/ANN-682
Project: Hibernate Annotations
Issue Type: New Feature
Components: binder
Reporter: Christian Bauer
Put this @ManyToOne in a @MappedSuperclass:
@ManyToOne(fetch = FetchType.LAZY)
@JoinColumn(name = "CREATED_BY_USER_ID", nullable = false)
// Ideally this foreign key should be ON DELETE SET NULL, however...
// Hibernate can't rename these so subclasses would get the same FK constraint
name. This doesn't
// work, so we need to let Hibernate create a random identifier for these. We could
fix this in the
// DatabaseObjects.hbm.xml file but we can't even address it because the name is
random. This sucks.
// So we do a manual SET NULL|DEFAULT when userHome.remove() is called.
// @org.hibernate.annotations.ForeignKey(name =
"FK_WIKI_NODE_CREATED_BY_USER_ID")
protected User createdBy;
Now all subclasses get that foreign key constraint name in the database catalog, which
isn't possible - constraint names have to be unique.
--
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