db-torque-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lach, Thierry" <Thierry.L...@bbdodetroit.com>
Subject RE: Info on jdbc task on Oracle
Date Mon, 02 Dec 2002 14:29:59 GMT
Please note that this does not appear to be a problem specific to
Oracle.  I have seen the same problem with DB2.

Perhaps Turbine could use DatabaseMetaData.storesUpperCaseIdentifiers()
and DatabaseMetaData.storesUpperCaseQuotedIdentifiers() to identify this
situation and convert the search string to uppercase prior to searching
(with an appropriate comment of course). 


-----Original Message-----
From: Andreou Andreas [mailto:andyhot@di.uoa.gr] 
Sent: Friday, November 29, 2002 1:59 PM
To: Turbine Torque Developers List
Subject: Info on jdbc task on Oracle

Martin Poeschl wrote:

> what was the problem with the jdbc task????

Actually the problem is not on the task, but in ORACLE's schema

Whenever a user is created on oracle, a schema with the same name is 
also created.
The catch is:
    1) Even though username and password is case insensitive, the schema

is NOT.
    2) The schema is created by uppercasing the username !!! So,for
ORACLE, in the build.properties, one should define the schema in 

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message