DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=30749>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=30749 Oracle 9.2.0 JDBC Timestamp Problem Summary: Oracle 9.2.0 JDBC Timestamp Problem Product: Commons Version: Nightly Builds Platform: PC OS/Version: Windows XP Status: NEW Severity: Enhancement Priority: Other Component: DbUtils AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] I just run into a Timestamp problem with the Oracle 9i (9.2.0) JDBC Driver. When calling rs.getObject(index) on a DB field, defined as Timestamp(6), the resulting object is a oracle.sql.TIMESTAMP and not a java.sql.Timestamp as with other JDBC Drivers. This leads to a null value propagation if your Bean Property is defined as java.sql.Timestamp. If calling rs.getTimestamp(index), Oracle correctly converts the resulting value to a java.sql.Timestamp object. The following addition to the processColumn Method of the BeanProcessor class whould solve the problem. } else if(propType.equals(Timestamp.class)) { return rs.getTimestamp(index); This ensures that for a Bean property of type java.sql.Timestamp the getTimestamp() method is called. Otherwise the default getObject() mehod is called, so there souldn't be a problem if someone wants the Oracle enhanced oracle.sql.TIMESTAMP object. Regards Rolf --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
