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] Updated: (DERBY-3871) EmbedBlob.setBytes returns incorrect insertion count
Date Fri, 03 Oct 2008 09:02:44 GMT

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

Kristian Waagan updated DERBY-3871:

    Attachment: derby-3871-1a_insertion_count.diff

Patch 1a contains a fix and the tests (from the previously attached repro/test).

* EmbedBlob
  JavaDoc fixes for setBytes methods.
  Fixed problem by ignoring return value from control.write().
  The write operation always writes the requested number of bytes, if not it fails (IndexOutOfBoundsException).

* LOBStreamControl
  JavaDoc fixes for write(byte[], int, int, long)

* jdbc4/BlobTest
  Added three tests.

Running full regression tests.
Patch ready for review.

> EmbedBlob.setBytes returns incorrect insertion count
> ----------------------------------------------------
>                 Key: DERBY-3871
>                 URL: https://issues.apache.org/jira/browse/DERBY-3871
>             Project: Derby
>          Issue Type: Bug
>          Components: JDBC
>    Affects Versions:
>            Reporter: Kristian Waagan
>            Assignee: Kristian Waagan
>         Attachments: BlobSetBytesTestRepro.diff, derby-3871-1a_insertion_count.diff
> EmbedBlob.setBytes returns invalid insertion counts. According to the JavaDoc, it should
return the number of bytes inserted. The current implementation seems to return the position
in the Blob after the bytes have been written.

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

View raw message