You are viewing a plain text version of this content. The canonical link for it is here.

Posted to derby-dev@db.apache.org by "Kristian Waagan (JIRA)" <ji...@apache.org> on 2007/05/15 17:20:16 UTC

[jira] Updated: (DERBY-2652) Clob.setCharacterStream differs between embedded and client driver

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

Kristian Waagan updated DERBY-2652:
-----------------------------------

    Attachment: ClobSetCharacterStreamTest.java

Attached repro 'ClobSetCharacterStreamTest.java'.

> 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.