[
https://issues.apache.org/jira/browse/BEANUTILS-142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12500267
]
Niall Pemberton commented on BEANUTILS-142:
-------------------------------------------
OK I didn't read carefully enough - the initial description seemed to indicate
it was an issue between java.sql.Date and java.sql.Timestamp - I'd missed the
point about oracle.sql.TIMESTAMP altogether. I'll revert the change I made
(which was accidental anyway).
> [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]
