Return-Path: 
 <torque-dev-return-4528-apmail-db-torque-dev-archive=db.apache.org@db.apache.org>
Delivered-To: apmail-db-torque-dev-archive@www.apache.org
Received: (qmail 96639 invoked from network); 19 Sep 2004 21:59:50 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur-2.apache.org with SMTP; 19 Sep 2004 21:59:50 -0000
Received: (qmail 63639 invoked by uid 500); 19 Sep 2004 21:59:42 -0000
Delivered-To: apmail-db-torque-dev-archive@db.apache.org
Received: (qmail 63552 invoked by uid 500); 19 Sep 2004 21:59:41 -0000
Mailing-List: contact torque-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:torque-dev-unsubscribe@db.apache.org>
List-Subscribe: <mailto:torque-dev-subscribe@db.apache.org>
List-Help: <mailto:torque-dev-help@db.apache.org>
List-Post: <mailto:torque-dev@db.apache.org>
List-Id: "Apache Torque Developers List" <torque-dev.db.apache.org>
Reply-To: "Apache Torque Developers List" <torque-dev@db.apache.org>
Delivered-To: mailing list torque-dev@db.apache.org
Received: (qmail 63526 invoked by uid 99); 19 Sep 2004 21:59:40 -0000
X-ASF-Spam-Status: No, hits=0.0 required=10.0
	tests=FORGED_RCVD_HELO
X-Spam-Check-By: apache.org
Received-SPF: neutral (hermes.apache.org: local policy)
Received: from [212.67.96.149] (HELO msgdirector2.onetel.net.uk)
 (212.67.96.149)
  by apache.org (qpsmtpd/0.28) with ESMTP; Sun, 19 Sep 2004 14:59:40 -0700
Received: from bolek.coachhouse (213-78-98-238.friaco.onetel.net.uk
 [213.78.98.238])
	by msgdirector2.onetel.net.uk (MOS 3.4.6-GR)
	with ESMTP id BWP75295;
	Sun, 19 Sep 2004 22:59:31 +0100 (BST)
Received: (Exim 3.36) #1 (Debian))
	protocol: esmtp
	id 1C99iK-0005D3-00
	; Sun, 19 Sep 2004 22:59:20 +0100
Message-ID: <414E0137.7040804@numerixtechnology.de>
Date: Sun, 19 Sep 2004 22:59:19 +0100
From: T E Schmitz <mailreg@numerixtechnology.de>
Reply-To: mailreg@numerixtechnology.de
User-Agent: Mozilla Thunderbird 0.7 (Windows/20040616)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Apache Torque Users List <torque-user@db.apache.org>,
        Apache Torque Developers List <torque-dev@db.apache.org>
Subject: case sensitive ORDER BY
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-Virus-Checked: Checked
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N

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: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org