RE: Info on jdbc task on Oracle

["Lach, Thierry" <Th...@bbdodetroit.com>]

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
support...

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 
uppercase.



--
To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
For additional commands, e-mail:
<ma...@jakarta.apache.org>

Re: Info on jdbc task on Oracle

[Andreou Andreas <an...@di.uoa.gr>]

Lach, Thierry wrote:

>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).
>
If anyone is interesting, i can submit a patch on
org.apache.torque.task.TorqueJDBCTransformTask
that makes use of DatabaseMetaData.storesUpperCaseIdentifiers() and
DatabaseMetaData.storesUpperCaseQuotedIdentifiers()