commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Henri Yandell (JIRA)" <>
Subject [jira] Commented: (BEANUTILS-142) [beanutils] RowSetDynaClass fails to copy resulset to DynaBean with Oracle 10g JDBC driver
Date Sat, 14 Jul 2007 02:09:04 GMT


Henri Yandell commented on BEANUTILS-142:

As we dig into it at the same time :)


3) Use Niall's patch.

This is a bit odd in that it means that the DATE column type will goto a java.sql.Date and
lose the time part [which may be all that is there given that Oracle lacks a TIME type]. 
Their metadata getColumnClassName says java.sql.Timestamp, the getColumnType says java.sql.Types.DATE,
and the getObject returns java.sql.Date. So I think that's 2 to 1 in favour of saying that
in Oracle you lose such things.

So I'm +1 to your patch Niall. It removes the try throwable bit, so that can be ignored from
my previous 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
>            Assignee: Henri Yandell
>             Fix For: 1.8.0
>         Attachments: beanutils-142-oracle-bug.patch, 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