[ https://issues.apache.org/jira/browse/BEANUTILS-142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12500254 ]
Henri Yandell commented on BEANUTILS-142: ----------------------------------------- The RowSetDynaClass change still uses getObject, which on Oracle will return oracle.sql.Timestamp which extends Object. So unless the convert lookup handles oracle.sql.Timestamp as a String, it's not going to work and people will have to register their own workaround converter (which we could put on a wiki or something). > [beanutils] RowSetDynaClass fails to copy resulset to DynaBean with Oracle > 10g JDBC driver > ------------------------------------------------------------------------------------------ > > Key: BEANUTILS-142 > URL: https://issues.apache.org/jira/browse/BEANUTILS-142 > Project: Commons BeanUtils > Issue Type: Bug > Components: DynaBean > Environment: Operating System: Windows XP > Platform: All > Reporter: Li Zhang > Fix For: 1.8.0 > > Attachments: Beanutils-142.patch > > > Beginning in Oracle 9.2, DATE is mapped to Date and TIMESTAMP is mapped to > Timestamp. However if you were relying on DATE values to contain time > information, there is a problem. When using Oracle 10g JDBC driver, the > ResultSetMetaData.getColumnClassName returns java.sql.Timestamp but > ResultSet.getObject(name).getClass() returns java.sql.Date. Obviously these > two > do not match each other. When the RowSetDynaClass.copy function tries to set > the > value to BasicDynaBean, it throws exception. Need a workaround. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]