[hibernate-dev] JDK 10 Early Access b33 and JDK 8u162 Early Access b03 are available on jdk.java.net

Hi Sanne, *JDK 10 Early Access  build 33 is available at : - **jdk.java.net/10/* Notable changes since previous email. JDK-8180019 - *javadoc treats failure to access a URL as an error , not a w

Re: [hibernate-dev] JPA Compliance

Wrt to bag versus list, it's more the inability to fetch multiple bags, which is perfectly legal in JPA but is an exception in Hibernate. If have to search for the exact section, but afair to JPA a List defined as OneToMany or ManyToMany has an implicit OrderColumn if one is not provided. And in

Re: [hibernate-dev] JPA Compliance

Makes sense. I think it's reasonable to add this since this is what a many-to-many table relationship looks like. But, it's ok to postpone it until 6.0. Vlad On Tue, Nov 28, 2017 at 12:38 PM, andrea boriero wrote: > It is not about the order but about duplicates. > > With the following > class

Re: [hibernate-dev] JPA Compliance

It seems fine to me and I agree to delay the @Bag to 6.0. On 27 November 2017 at 21:29, Steve Ebersole wrote: > So then how about the following: > > >1. Add a multi-valued setting to define various categories of JPA >compliance. E.g. `hibernate.jpa.compliance` with multi-selectable valu

Re: [hibernate-dev] JPA Compliance

It is not about the order but about duplicates. With the following class A { List bsl @JoinTable(name = "A_B", joinColumns = @JoinColumn(name = "A_ID"), inverseJoinColumns = @JoinColumn(name = "B_ID"), ) @ManyToMany public List getBs() { return b; } } class *B*{ List as; ..