db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <j...@apache.org>
Subject [jira] Closed: (DERBY-2652) Clob.setCharacterStream differs between embedded and client driver
Date Wed, 20 Jun 2007 11:38:26 GMT

     [ https://issues.apache.org/jira/browse/DERBY-2652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Kristian Waagan closed DERBY-2652.

       Resolution: Fixed
    Fix Version/s:

I agree with Øystein and I close the issue as fixed.
Note that the difference in behavior is still there for 10.2, but it has been fixed for 10.3
with the change to locator based LOBs.

> 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:,
>            Reporter: Kristian Waagan
>             Fix For:
>         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

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message