Hi,
There is a small patch in JIRA (HHH-2440) that allows the user to
specify that the generated SQL should not contain the distinct keyword.
Mike.
Steve Ebersole wrote:
The in-memory distincting is actually a temporary solution. There are a
few JIRA cases making up the ultimate solution.
The in-memory distincting is actually a temporary solution. There are a
few JIRA cases making up the ultimate solution.
But specifically to your questions, the DISTINCT applied to the query is
intended to limit the data transferred by the JDBC driver from server to
client, especially on
Thanks Steve,
Could you point me to the JIRA tasks, I would be interesting in seeing
what the ultimate solution looks like?
The thing that confuses me is that distinct generally doesn't come for
free (generally resuls in a sort by the DB). If the result set is going
to be the same anyway,
On Feb 19, 2007, at 3:32 PM, Michael Barker wrote:
However I have noticed that everytime distinct is specifed in the
ejb-ql query it also gets specified in the sql query. I am
curious as the reasoning behind this.
You are wondering why a DISTINCT you put into your query is actually
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,
Michael Barker.
___
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.
