[
https://issues.apache.org/jira/browse/BEANUTILS-142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Niall Pemberton updated BEANUTILS-142:
--------------------------------------
Affects Version/s: 1.7.0
Summary: RowSetDynaClass fails to copy ResultSet to DynaBean with
Oracle 10g JDBC driver (was: [beanutils] RowSetDynaClass fails to copy
resulset to DynaBean with Oracle 10g JDBC driver)
> RowSetDynaClass fails to copy ResultSet 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
> Affects Versions: 1.7.0
> Environment: Operating System: Windows XP
> Platform: All
> Reporter: Li Zhang
> Assignee: Henri Yandell
> Fix For: 1.8.0
>
> Attachments: beanutils-142-oracle-bug.patch, Beanutils-142.patch,
> Play.java
>
>
> 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]
