[
https://issues.apache.org/jira/browse/DERBY-2652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12496215
]
Øystein Grøvlen commented on DERBY-2652:
----------------------------------------
I would assume the behavior should be the same as for Clob.setString. This
isssue was raised in DERBY-1286 and Lance presented the opinion of the expert
group in the following thread:
http://www.nabble.com/-jira--Created%3A-%28DERBY-1286%29-Fill-in-Clob-methods-required-for-JDBC3-compliance-tf1553591.html#a4549524
This discussion indicates that the embedded has the right behavior. (That is
also similar to the current client behavior for Blobs.)
When using locators the client will forward the operation to the server.
Hence, this difference should disappear when locators are enabled for Clobs.
--
Øystein
> Clob.setCharacterStream differs between embedded and client driver
> ------------------------------------------------------------------
>
> Key: DERBY-2652
> URL: https://issues.apache.org/jira/browse/DERBY-2652
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.3.0.0
> Reporter: Kristian Waagan
> Attachments: ClobSetCharacterStreamTest.java
>
>
> Clob.setCharacterStream behaves differently depending on whether you use the
> embedded or the client driver.
> Sample output from the repro:
> (embedded) Initial : 123456789
> (embedded) After : 12__56789
> (client) Initial : 123456789
> (client) After : 12__
> As can be seen, the client driver truncates the Clob value when it writes to
> it, whereas the embedded driver does not and instead replaces existing
> characters with those written to the character stream.
> (BTW: I know the title is not perfectly accurate, but it got so long when
> explaining that it is when you actually write to the stream returned by
> Clob.setCharacterStream the result differs.)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
