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 13:58: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-2a-loop_fix.diff

Sorry Knut Anders, I committed just before I saw your comment...

Regarding the @since tags, I asked the community to comment on the issue. I will correct the
tags later.

Actually, the loop is incorrect :) It will write too much data, unless the data length is
a multiple of the buffer size. It also requires the stream to be well behaved (always returning
the requested number of bytes).
I've fixed the problem in patch 2a.

Thanks for the 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
>             Fix For:
>         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