[
https://issues.apache.org/jira/browse/DERBY-1599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12539562
]
Kristian Waagan commented on DERBY-1599:
----------------------------------------
It is not clear to me why getCharacterStream and updateCharacterStream count as
two read operations on a column.
>From a users point of view, I'm updating the column, reading it back (for some
>reason...) and then finally performing the update (updateRow, not commit).
>This fails in trunk for stream, but I assume it works for primitives?
The other way around (equals what Dan asked in the previous comment), I read
the current column value, supply new data and tell Derby to update the row. I
believe this works in trunk?
To be able to implement something that is consistent and robust, I think we
have to investigate and specify what exactly is allowed.
> Clob.getSubString() throws NullPointerException when created by updatable
> result set
> ------------------------------------------------------------------------------------
>
> Key: DERBY-1599
> URL: https://issues.apache.org/jira/browse/DERBY-1599
> Project: Derby
> Issue Type: Bug
> Components: JDBC, Network Client
> Affects Versions: 10.1.3.1, 10.2.1.6
> Reporter: Knut Anders Hatlen
> Priority: Minor
> Attachments: Repro.java
>
>
> If you create a clob value with one of the ResultSet.updateXXX methods that
> take a stream or a reader, and retrieve that value with ResultSet.getClob(),
> a NullPointerException will be thrown when getSubString() is called on the
> returned Clob object. This happens with the network client driver, and it has
> been observed on Derby 10.1.3.1 and trunk.
> Exception in thread "main" java.lang.NullPointerException
> at org.apache.derby.client.am.Clob.getSubStringX(Clob.java:229)
> at org.apache.derby.client.am.Clob.getSubString(Clob.java:210)
> at Repro.main(Repro.java:24)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
