db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas Korneliussen (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-1421) ResultSet.updateBinaryStream fails when the result type is TYPE_SCROLL_INSENSITIVE
Date Fri, 30 Jun 2006 08:15:31 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1421?page=all ]

Andreas Korneliussen updated DERBY-1421:

    Attachment: derby-1421v2.diff

As part of fixing DERBY-802, I found that the call to rowChanger.updateRow(..) has destructive
effect on the Blob columns, so that they cannot be used again in source.updateRow(..) when
doing clone or if it is to be used for writing it into a disk hash table.

I have therefore replaced the order of the calls in UpdatableResultSet.java, so that they
are now:


This means that the hashtable in ScrollInsensitiveResultSet will be updated before the actual
row is updated, however from the user this is atomic.

With the patch derby-1421v2.diff, I have kept all the tests in derby-1421.diff, however I
have removed the changes in SQLBinary. The test passes.

Using this patch, in combination with the removal of cloning in DERBY-802 I have been able
to read and update 64MB blobs in scrollable insensitive result sets.

> ResultSet.updateBinaryStream fails when the result type is TYPE_SCROLL_INSENSITIVE
> ----------------------------------------------------------------------------------
>          Key: DERBY-1421
>          URL: http://issues.apache.org/jira/browse/DERBY-1421
>      Project: Derby
>         Type: Bug

>   Components: JDBC
>     Versions:
>     Reporter: V.Narayanan
>     Assignee: Fernanda Pizzorno
>  Attachments: TestUpdateBinaryStream.java, derby-1421.diff, derby-1421.stat, derby-1421v2.diff
> Attaching test program for the above bug. The program however works fine when the ResultSetType

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message