[
https://issues.apache.org/jira/browse/DBUTILS-111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13715434#comment-13715434
]
Edmond Kemokai edited comment on DBUTILS-111 at 7/22/13 5:54 PM:
-----------------------------------------------------------------
I should add that while it would be nice to fix this in the main distribution,
one can easily overcome this issue by extending the row processor
implementations.
was (Author: bitlooter):
I should add that while it will be nice to fix this in the main
distribution, one can easily overcome this issue by extending the row processor
implementations.
> Multiple calls to getObject on stream columns causes exception
> --------------------------------------------------------------
>
> Key: DBUTILS-111
> URL: https://issues.apache.org/jira/browse/DBUTILS-111
> Project: Commons DbUtils
> Issue Type: Bug
> Affects Versions: 1.5
> Reporter: Edmond Kemokai
> Priority: Minor
> Original Estimate: 12h
> Remaining Estimate: 12h
>
> I use derby and it doesn't allow more than one call to
> rs.get[Object|Clob|Blob|AsciiStream|CharacterStream|BinaryStream] on a the
> same column in a resultset row.
> In BeanProcessor.processColumn (and possibly other places in dbutils), there
> is a null check against rs.getObject at the beginning of the function. When
> the column being retrieved is a clob/blob column, this will throw an
> exception on derby because when you make the subsequent
> get[Object|Clob|Blob|AsciiStream|CharacterStream|BinaryStream] call, it
> counts as more than one retrieval request.
> The fix will be a rewrite to ensure clob/blob/stream columns are retrieved
> only once per resultset row.
> You can find more information on the derby team thought process on this issue:
> http://db.apache.org/derby/releases/release-10.6.1.0.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
