Filed bug https://hibernate.atlassian.net/browse/HHH-10519; Reproducer
is at
https://github.com/gunnarmorling/hibernate-test-case-templates/commit/3c5507755f83039fe40eac7daaa9f1060d97e426.
--Gunnar
2016-02-11 15:13 GMT+01:00 Steve Ebersole :
> We can make that change in SQM, but its not an opt
We can make that change in SQM, but its not an option to change that
before.
But Gunnar your load use case would be a bug if true
On Thu, Feb 11, 2016, 7:55 AM Vlad Mihalcea wrote:
> Hi,
>
> True. I also wondered why don't we use the DISTINCT as the default
> mechanism.
> While the underlying
Hi,
True. I also wondered why don't we use the DISTINCT as the default
mechanism.
While the underlying SQL would return a result-set according to the total
number of joined relations, we are building the entity tree hierarchy and
I don's see why a user would be interested in getting duplicate root
Hi,
I understand that $subject is a known source of confusion for people
when working with HQL/criteria queries and not applying something like
DistinctRootEntityResultTransformer.
I am seeing the same behaviour though when getting a root entity by id
and join-fetching two (nested) collections. T
