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-3978) Clob.truncate(long) in the client driver doesn't update the cached Clob length
Date Mon, 08 Dec 2008 14:22:44 GMT

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

Kristian Waagan updated DERBY-3978:
-----------------------------------

    Attachment: derby-3978-2a-update_length.diff

Patch 2a is a simple fix for the bug.
Another option is to pull both updates out of the if-else block.

Running regression tests.
Patch ready for review.

> Clob.truncate(long) in the client driver doesn't update the cached Clob length
> ------------------------------------------------------------------------------
>
>                 Key: DERBY-3978
>                 URL: https://issues.apache.org/jira/browse/DERBY-3978
>             Project: Derby
>          Issue Type: Bug
>          Components: JDBC, Network Client
>    Affects Versions: 10.3.3.0, 10.4.2.0, 10.5.0.0
>            Reporter: Kristian Waagan
>            Assignee: Kristian Waagan
>         Attachments: derby-3978-1a-regression_tests.diff, derby-3978-2a-update_length.diff
>
>
> The client driver caches the Clob length, but doesn't update it when Clob.truncate is
called.
> I will attach a few regression tests, where one of them demonstrates the issue. The fix
is also very simple; update the cached length.

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


Mime
View raw message