Re: Table not found with jdbc sql statement

"Simon Bieri" <Simon.Bieri_at_sisclear.com> wrote in message news:bnr4kp$14k68e$1_at_ID-151365.news.uni-berlin.de...
> Thanks for your answers.
>
> Niall Litchfield schrieb:
>
> <SNIP>
>
> > I don't have a working java ide at the moment to test out what is
happening,
> > and in any case we haven't seen the java code that tries to select from
the
> > table.
>
> ...
>
> >> From my point of view using double quotes for table names is a bad
habit
> >
> > and
> >
> >>should be avoided at all.
> >
> >
> > This I entirely agree with.
>
> I'm not.
>
> To change that "bad habit" is not that easy, because all sql statements
> and connections to the database are in a java package (based on
java.sql.*).
> Anyway, I agree with Thomas Kellerer, that 'the SQL standard says that
> as soon as you put an object in double quotes, the database has to
> handle that case sensitive'. So that means, when I create the tables
> with my sql script, Oracle should be able to find the table names in
> double quotes and mixed case. The question is now, does Oracle fully
> support the SQL standard?

That was really what the sqlplus cut and paste was supposed to demonstrate. It shows that as soon as you put an object in double quotes Oracle handles it as case sensitive. in other words your code really does create a case sensitive tablename that needs case sensitive handling.

I have now installed java sdk 1.4 and the test case behaves as I expected.

the code

import java.io.*;

import java.sql.*;

public class MixedCase

{

private static Connection conn;

private static Statement stmt;

private static ResultSet rset;

public static void main (String[] args) throws SQLException, ClassNotFoundException

{

Class.forName ("oracle.jdbc.driver.OracleDriver");

conn = DriverManager.getConnection

("<connection string");

stmt = conn.createStatement ();

rset = stmt.executeQuery( "SELECT \"DateTime\" FROM \"DbTableOne\"" );

}

}

compiles and works fine against the database that I ran your sql on earlier. - i.e Ora-00942 is not thrown. What does your code look like?

-- 
Niall Litchfield
Oracle DBA
Audit Commission Uk