Re: [hibernate-dev] Naming strategies and join tables

2016-02-22 Thread Steve Ebersole
It is also important to understand that lots of Hibernate code calling into NamingStrategy did so in quite inconsistent ways. We decided that consistency of the calling was more important moving forward. So while ImplicitNamingStrategyLegacyJpaImpl strives to be compatible with the older EJB3Nami

Re: [hibernate-dev] Naming strategies and join tables

2016-02-22 Thread Guillaume Smet
Important point: AbstractProjet uses SINGLE_TABLE inheritance. On Mon, Feb 22, 2016 at 12:10 PM, Guillaume Smet wrote: > Hi, > > I'm migrating another application to 5.x and have the following issue with > the new naming strategies. > > We used EJB3NamingStrategy and are now using > ImplicitNami

[hibernate-dev] Naming strategies and join tables

2016-02-22 Thread Guillaume Smet
Hi, I'm migrating another application to 5.x and have the following issue with the new naming strategies. We used EJB3NamingStrategy and are now using ImplicitNamingStrategy*Legacy*JpaImpl which is advertised as being its replacement. The model is the following: @Entity AbstractProjet > @