commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Niall Pemberton (JIRA)" <>
Subject [jira] Commented: (BEANUTILS-142) [beanutils] RowSetDynaClass fails to copy resulset to DynaBean with Oracle 10g JDBC driver
Date Wed, 27 Jun 2007 19:35:26 GMT


Niall Pemberton commented on BEANUTILS-142:

OK I don't have strong opnions on this issue - in the absence of other opnions I'll leave
the change I committed accidently in. If anyone thinks that it should be removed then I don't
have a problem with that either. Either way (or alternative solutions) I'd like to get to
a point where we can close this.

P.S. dyna bean - please don't delete previous comments you made - it makes the thread of comment

> [beanutils] RowSetDynaClass fails to copy resulset to DynaBean with Oracle 10g JDBC driver
> ------------------------------------------------------------------------------------------
>                 Key: BEANUTILS-142
>                 URL:
>             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:
For additional commands, e-mail:

View raw message