Hi Tarlika,
I did not look at the code, but in Torque 3.1.1-rc2, Henning has completely
rewritten the handling of order by, so this might be incorporated in the
latest Release Candidate. If this is the case, you could get the relevant
code from there and put it into you modified BasePeer.
I plan to incorporate these changes and the suggestions by Scott in my
patch, but as I do have little time during the next weeks, this could well
take till the middle of October.
Thomas
T E Schmitz <[EMAIL PROTECTED]> schrieb am 19.09.2004 23:59:19:
> Hello,
>
> I am using Torque 3.1 with PostgreSQL 7.4.
>
> I noticed that the generated ORDER BY clause is always case insensitive.
> Regardless of Criteria.setIgnoreCase(), for Strings the ORDER BY clause
> always uses UPPER(<col>). I had a look at
> BasePeer.processOrderBy(), which always calls
> db.ignoreCaseInOrderBy(orderByColumn) for Strings.
>
> Is this intended?
> How can a case sensitive ORDER Bbe produced?
>
> (processOrderBy() was introduced by Thomas Fischer for the outer join
> patch but this particular piece of code is identical to the original in
> createQuery())
>
> --
>
>
> Regards/Gru�,
>
> Tarlika Elisabeth Schmitz
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
