[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5390?page=c...
]
Gail Badner commented on HHH-5390:
----------------------------------
The many-to-one side is the owner of a many-to-one/one-to-many association.
From JSR-317:
2.9 Entity Relationships:
"The many side of one-to-many / many-to-one bidirectional relationships must be the
owning
side, hence the mappedBy element cannot be specified on the ManyToOne annotation."
11.1.36 OneToMany Annotation:
In table 33, the description for MappedBy is:
"The field or property that owns the relation-
ship. Required unless the relationship is uni-
directional."
Index column on inverse List should throw a warning
---------------------------------------------------
Key: HHH-5390
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5390
Project: Hibernate Core
Issue Type: Improvement
Components: annotations
Affects Versions: 3.5.3
Reporter: Chris Bredesen
The manual correctly warns against trying to map an indexed inverse collection on a List.
However, a configuration containing this invalid mapping builds successfully but causes
null values to be inserted for the index column.
Hibernate should be helpful and, if possible, throw a warning to the user (perhaps an
error?) that explains the invalid combination. Here is an example that would run but
produce invalid results:
{code}
@Entity
public class Parent {
@OneToMany(mappedBy="parent")
@OrderColumn(name="order")
private List<Child> children;
}
@Entity
public class Child {
@ManyToOne
private Parent parent;
}
{code}
The above is a typical one to many with the addition of @OrderColumn. Because Child owns
the relationship, the index column is lost/ignored. Hibernate should warn about this.
--
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