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:[EMAIL PROTECTED]] 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: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
