Patch applied to both STABLE and HEAD branches.
I also added a test case that demonstrates the problem that Scott
described, and of course shows that it goes away with this fix.
Andrus
On Friday, October 10, 2003, at 09:02 PM, Scott Finnerty wrote:
> I reworked the changes to SelectTranslator to ensure a unique column
> set.
>
> I looked and since I don't alter the "official" column list in
> SelectTranslator, and it creates the ResultDescriptor from that column
> list,
> the DefaultResultIterator should not be affected by these changes.
>
> Scott
>
> -----Original Message-----
> From: Scott Finnerty [mailto:scot..odefuey.com]
> Sent: Friday, October 10, 2003 1:23 PM
> To: cayenne-deve..bjectstyle.org
> Subject: RE: Patch for DISTINCT, ORDER BY issue
>
> I'll rework the change to ensure a unique column set - but you do
> understand
> that in order to comply with the database restrictions that the
> following
> will still likely occur: SELECT DISTINCT .... t0.NAME, ...
> UPPER(t0.NAME)
> ... ORDER BY UPPER(t0.NAME)? So some extra baggage is unavoidable in
> this
> instance (with the case insensitive order by) if we are to address the
> issue.
>
> I'll have a look at the DefaultResultIterator to see what effect my
> change
> may have had.
>
> Thanks,
> Scott
This archive was generated by hypermail 2.0.0 : Mon Oct 13 2003 - 00:50:35 EDT