Message:
A new issue has been created in JIRA.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-299
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-299
Summary: Reuse of primary key in one-to-one realtion with subclasses
Type: Bug
Status: Unassigned
Priority: Minor
Project: Hibernate2
Components:
core
Versions:
2.0rc2
2.1
2.0 final
2.0.1
2.0.2
2.0.3
2.1 beta 1
2.1 beta 2
Assignee:
Reporter: Johan Granlund
Created: Fri, 29 Aug 2003 4:50 AM
Updated: Fri, 29 Aug 2003 4:50 AM
Environment: Doesn't matter
Description:
In a flight planning system. I got three entities, Staion, Leg and Movement. A Leg is a combination of a Departure and a Arrival. Departure and Arrival are subclasses of Movement. Movement has a relation to Station and holds a time.
Leg has one one-to-one relation with Arrival and one one-to-one relation with Departure.
Since hibernate force you to reuse the primary key in one-to-one relations tou can't setup above since Departue and Arrival shares the same table.
This is just one example when reuse of primary keys is annoying even worse is when you use composite primary keys.
---------------------------------------------------------------------
JIRA INFORMATION:
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.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
