ql "select
distinct...".
Regards,
Michael Barker.
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
___
hibernate-dev mailing list
hiber
You are wondering why a DISTINCT you put into your query is actually
send to the database in the generated SQL?
Yes, or more specifically, why DISTINCT is sent to the database in cases
where result set will be the same with or without the DISTINCT clause.
___
JIRA is searchable. Look for things marked as 'query-hql' as the
component... The basic idea is to drop the collection-valued fetches.
Is this where you will fetch collections in a sub-select rather than a join?
Regards,
Mich
nyway, isn't there an advantage to excluding the
distinct clause, or is it simply not possible to determine which queries
will benefit from it and which won't?
Regards,
Michael Barker.
Steve Ebersole wrote:
The in-memory distincting is actually a temporary solution. There are
a few JI
I assume that the distinct is in there for are reason,
are there some more complicated use cases for which the distinct in
necessary?
My main concern is performance, is there anyway of performing an ejb-ql
"select distinct..." without hibernate issuing an sql "select distinc
