Hello Thomas, Thanks for your reply.
A few thoughts on case sensitivity:
I think it would be desirable to have the flexibility to decide separately for ORDER BY and the search itself whether they are to be case sensitive or not.
I am not quite sure what exactly Criteria.setIgnoreCase() has an effect on right now (in v3.1). But if you wanted, say, a case sensitive ORDER BY and case insensitive search criteria, one flag wouldn't do the job.
You would probably need something like an SqlEnum.IEQUAL and SqlEnum.ILIKE and the corresponding negative operators.
Regards/Gru�,
Tarlika
Thomas Fischer wrote:
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:
Is this intended? How can a case sensitive ORDER Bbe produced?
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
