We discussed this before on the list. The main thing to decide is
Session#load and proxies. Basically there are times when:
public T load(Class<T> entityType, Object id)
simply will not work. This is the discussion I started wrt annotating the
proxy interface, rather than the impl class.
Basically I am not going to do this work piecemeal. When we add typing, I
will add it everywhere at once. So as soon as we can come up with an
elegant solution for that, I can add that to the roadmap. And please see
the previous discussion before we just start re-hashing the same points
over and over :) It was a quite long thread.
On Wed, Apr 29, 2015 at 4:14 AM, Emmanuel Bernard <emmanuel(a)hibernate.org>
wrote:
Hi Vlad,
That’s an interesting proposal. It is certainly possible. But since the
Session and Query API (Hibernate native) is historically non typed, I
wonder if that is worth introducing these new typed version and add more
overloaded methods on Session.
Do you think it is worth the additional complexity?
Steve, do you have some plan for a Session API revamp some time in the
future? Some spring cleaning of sort.
Emmanuel
> On 15 Apr 2015, at 22:27, Mihalcea Vlad <mih_vlad(a)yahoo.com> wrote:
>
> Hi,
> Although many rely on the Java Persistence API, Hibernate still offers
specific features, like mapping a native SQLQuery result set to a DTO:
> .setResultTransformer(Transformers.aliasToBean(DTO.class));
> Is it possible to add TypedQuery and TypedSQLQuery, analogous to the JPA
specs, so you can use generics with specific API?
> Adding new interfaces and some overloaded Session methods wouldn't break
backward compatibility.
>
> Vlad MiIhalcea
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/hibernate-dev
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev