On 27 Jan 2014, at 15:17, Steve Ebersole wrote:
> So this is another representation of a choice we are having to make quite a
> bit in 5.0 development... correctness versus "legacy", which has really
> implications for users. So if users are relying on this Hibernate "feature"
> of splitting
So this is another representation of a choice we are having to make quite a
bit in 5.0 development... correctness versus "legacy", which has really
implications for users. So if users are relying on this Hibernate
"feature" of splitting identifier mapping annotations between the entity
and the IdC
This code is 8 years old so no I did not remember.
I did some archeology. The Git migration slots all of that history so I
had to fire up svn.
svn checkout
https://svn.jboss.org/repos/hibernate/annotations/branches/v3_4_0_GA_CP/
svn annotate src/test/java/org/hibernate/test/annotations/cid/OrderL
No idea. I think Emmanuel had a better understanding of the derived identifier
logic.
On 27 Jan 2014, at 06:26, Steve Ebersole wrote:
> What's the rational for supporting the following?
>
>
> @Entity
> class Product {
>...
> }
>
> @Entity
> class Order {
>...
> }
>
> @Entity
> @I
What's the rational for supporting the following?
@Entity
class Product {
...
}
@Entity
class Order {
...
}
@Entity
@IdClass(...)
class OrderLine {
@Id
private Order order;
@Id
private Product product;
}
Specifically, the declaration of the OrderLine primary key. Why
