+1 I see no problem either.
On 17 November 2017 at 15:57, Steve Ebersole <st...@hibernate.org> wrote: > Actually its possible that the TCK always tested it and merging > `javax.persistence.Query` and `org.hibernate.query.Query` may be the > culprit. But either way, the net result is the same... > > On Fri, Nov 17, 2017 at 8:44 AM Steve Ebersole <st...@hibernate.org> wrote: > >> I wont bore everyone with the history here, but long story short is that >> we need to start treating JPA "positional" parameters as positional in the >> `javax.persistence.Parameter#getPosition` sense. Even though there is >> nothing positional about JPA's positional parameters, this has moved from a >> philosophical discussion to a practical one as the JPA 2.2 TCK is testing >> this, whereas older ones did not >> >> To do that however, we need to drop our older positional parameter >> support. That feature has been deprecated for quite some time now. Unless >> there are objections, I will plan on dropping that in 5.3 >> > _______________________________________________ > 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
