db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dag H. Wanvik (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-6681) Cannot update BLOB/CLOB values in multiple rows simultaneously
Date Fri, 01 Aug 2014 15:28:39 GMT

    [ https://issues.apache.org/jira/browse/DERBY-6681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14082341#comment-14082341

Dag H. Wanvik commented on DERBY-6681:

Hi Holger, I tend to agree with you; one would expect the database to save a copy of the blob
if it needs it more than once. The reason I asked is that sometimes, requirements on lobs
are less stringent than for simple data types. So, I am ok with keeping this as a "bug", not
an "improvement". As for the blocker thing, we keep the user's opinion on the "Priority" field,
and use the "Urgency" field for devs. We are in a release phase for 10.11 right now, so if
you need an urgent solution, I'd recommend re-writing the app to work around it, or try to
roll your own patch. I am sure we'll consider this issue for the next major release, though.

> Cannot update BLOB/CLOB values in multiple rows simultaneously
> --------------------------------------------------------------
>                 Key: DERBY-6681
>                 URL: https://issues.apache.org/jira/browse/DERBY-6681
>             Project: Derby
>          Issue Type: Bug
>          Components: Store
>    Affects Versions:,
>            Reporter: Holger Rehn
>            Priority: Blocker
>         Attachments: MultiLOB.java
> When trying to execute a single command to update multiple rows with a new BLOB/CLOB
value, an exception is thrown because Derby tries to read the data stream once for every value/row
to update.

This message was sent by Atlassian JIRA

View raw message