Re: [hibernate-dev] 6.0 - ResultTransformer
On Tue, Sep 13, 2016 at 2:26 AM Gunnar Morling <gunnar(a)hibernate.org> wrote:
> Between dynamic-instantiation, Tuple-handling...
To be sure, WDYM by "tuple-handling"?
javax.persistence.Tuple
So I gave just one example earlier of how all of these things do not
necessarily fit together in inherently obvious ways. Some combinations I
think are ok; others are not. In sitting here and trying to describe this
to a user from a documentation perspective, it is not a simple explanation.
I'll follow up with a separate reply that covers those combos for
discussion.
One use case for result transformers are full-text searches executed
through Hibernate Search's Session extension FullTextSession (see
[1]).
For full-text searches we don't use HQL/JPQL, so the "new ..." syntax
cannot be used, but I don't know about tuple-handling.
Well for sure you do not allow the user to use HQL/JPQL. But I'd have to
assume that under the covers you handle resolving that FullTextQuery
yourself from the indexes - which means this is not even a ORM Query at all
and what we do with ResultTransformer in ORM in regards to Query is
completely irrelevant for you. In other words I would have to think that
Search itself is applying that ResultTransformer in your example, not ORM.
Very different.