That's a good question. There are some methods which don't have a replacement in JPA so we should probably move to some subclass and remove the deprecated flag.
Vlad On Wed, Aug 30, 2017 at 5:59 PM, Guillaume Smet <guillaume.s...@gmail.com> wrote: > Hi, > > In OGM tests, we have a lot of warnings on this sort of constructs: > NativeQuery query = session.createNativeQuery( nativeQuery ).addEntity( > OscarWildePoem.class ); > because addEntity() comes from SQLQuery and SQLQuery is deprecated. > > I don't think it's a good thing for our users as they have a warning and > they can't really do anything about it. > > I have a vague rememberance of a discussion about it a few months ago but > I don't remember the outcome of it. > > Shouldn't we copy all the non deprecated methods of SQLQuery to NativeQuery > so that our users don't get a warning? > > Or maybe I missed something? > > Thanks! > > -- > Guillaume > _______________________________________________ > hibernate-dev mailing list > hibernate-dev@lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev > _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
