Regression between jdbc thin version 9 and 10.1.0.3

Question

Hi all,
I tried to get a Date columns as a String with a specific format using the following technique:
dStatement = connection.createStatement();
dStatement.execute("alter session set NLS_DATE_FORMAT='YYYY-MM-DD HH24:MI:SS'");
((OracleStatement)dStatement).defineColumnType(1, Types.VARCHAR);
ResultSet rs = dStatement.executeQuery("select aDateColumn from...");
rs.next();
String aDate = rs.getString(1);
it worked fine in 9.2.0.5, but it failed on 10.1.03. I gives me the standard oracle format, which has got a .0 after the seconds.
Actually, in 10.1.0.3, I can do :
((OracleStatement)dStatement).defineColumnType(999, Types.VARCHAR);
and then execute a query that return 1 columns without even an exception.
Any workarounds not involving to_char() and getDate()?

Answer 1

The application works in windows machines (mainly
Windows 2003), running .Net and in Linux running
JBoss.
In Windows, we use the usual fat client (OCI) - MS
drivers for Oracle. Which data access methods or APIs are you using?
Microsoft's .Net provider for Oracle "requires Oracle Client software 8.1.7 or later". MS' other drivers from back in the days are designed for Oracle 7 and possibly 8.0.x, but no later.
Why are you not using Oracle's drivers "for Oracle"?
In Java, we use the thin client.>
We have now a new customer that has 10.1.0.3.0, and
due to other existing applications, he can't upgrade.Is that on the db side or app server?
>
We've made lots of tests in 10.2.0.3.0, and have now
some clients using it in this version.
I just need the RDBMS and client drivers changes (if any).Your app is closest to client drivers and if you have made a lot of tests, perhaps you should stick to this version of Client. The db side is slightly different. Oracle certifies interoperability between Net client and server. So I guess you need to map out which db specific features you are using and any install scripts, management procedures, etc. that may differ.
I would assume that from a 10.1 to a 10.2, no
change could break my code, but unfortunately my
experience taught me not to be so confident.Obi One has taught you well...