Well first I'd probably ask on user communication channels, not the
developer mailing list. That said, have you read the User Guide,
especially the revamped User Guide in 5.1?
On Tue, Feb 23, 2016 at 7:13 AM Adriano Santos
wrote:
> First all, where (exactly) can I get the correct way to mapping
First all, where (exactly) can I get the correct way to mapping all the
relations? We are always finding many differents mapping forms and this can
be terrible to beginners. I still dont know if we have some tutorial or
book like that, but I'd like... Anybody here knows?
Este e-mail foi enviado po
Well first, technically isn't that mapping incorrect? That should use
@CollectionTable rather than @JoinTable. I am not sure that makes a
difference, but in the interest of mapping things properly...
That being said... the whole premise of the legacy EJB3NamingStrategy was
to prefer the use of t
To be honest I cannot make up my mind to decide which behavior is more correct.
I can see both as valid.
> On 22 Feb 2016, at 18:07, Steve Ebersole wrote:
>
> It is also important to understand that lots of Hibernate code calling into
> NamingStrategy did so in quite inconsistent ways. We deci
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
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
