Ojdbc6.jar ojdbc14.jar anamoly and a bug

Question

PROGRAM
PreparedStatement ps = connection.prepareStatement( "select dob from pers", ResultSet.TYPE_SCROLL_INSENSITIVE, ResultSet.CONCUR_UPDATABLE);
ResultSet.getString("dob");
Output:
ojdbc14.jar:
*6/1/2012 0:0:0*
ojdbc6.jar:
*2001-06-01 00:00:00*
Why the difference? Is this a bug? Is there a fix? I require ojdbc6 output to be the same as ojdbc14. How can I achieve that? (Yes, I know its good to use ResultSet.getDate(...) instead of ResultSet.getString(...) etc etc but this is legacy code and there are too many occurrences for me to change all of them.)
Edited by: 935389 on May 18, 2012 3:51 PM

Answer 1

1. Get a Timestamp instead of a string.
2. Format the string in SQL and stop relying on the JDBC to do it.I quote again from my first post,
(Yes, I know its good to use ResultSet.getDate(...) instead of ResultSet.getString(...) etc etc but this is legacy code and there are too many occurrences for me to change all of them.)
No. Both values are correct they are just formatted differently. And the spec says nothing about how it formats strings.Java ResultSet API does not say anything about the format but this was not caused by Java6. It was ojdbc6.jar.
Also, the result is the same if I don't use,
ResultSet.TYPE_SCROLL_INSENSITIVE, ResultSet.CONCUR_UPDATABLEIt is not good to simply change format even though Oracle JDBC didn't specify any format either. Does this mean I'll have to test everything that is not specified in their spec? It is a bug.
Edited by: 935389 on May 20, 2012 5:21 PM