Mailing-List: contact torque-user-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Torque Users List" <torque-user@db.apache.org>
Received-SPF: pass (asf.osuosl.org: local policy)
Message-ID: <43DAF6AE.90002@nokia.com>
Date: Fri, 27 Jan 2006 20:44:30 -0800
From: Robert Dietrick <robert.dietrick@nokia.com>
User-Agent: Thunderbird 1.5 (Windows/20051025)
MIME-Version: 1.0
To: Apache Torque Users List <torque-user@db.apache.org>
Subject: case insensitive queries
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

I'm having difficulties getting a portion of my WHERE clause to be case 
insensitive with Oracle, and I'm wondering if this problem's been solved 
already.

I've tried Criteria.setIgnoreCase(true), which forces all parts of the 
WHERE clause to ignore case, and I've tried 
Criterion.setIgnoreCase(true), which does absolutely nothing (does this 
work with other databases???).

I've also tried the custom route: Criteria.add(columnName, 
"UPPER("+columnName+") = " + someValue.toUpperCase()).  But this is 
inherently dangerous when the value (someValue) is coming from an end 
user.  (May allow users to execute arbitrary SQL.)

What I want is something which results in the left half being converted 
to upper case and the right half still using a bind variable:
UPPER(columnName) = ?

Anyone know if this is possible?  I'm using the latest version (3.2).

Thanks.

-rob


---------------------------------------------------------------------
To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org
For additional commands, e-mail: torque-user-help@db.apache.org