You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Kristian Waagan (JIRA)" <ji...@apache.org> on 2008/12/08 15:18:44 UTC
[jira] Updated: (DERBY-3978) Clob.truncate(long) in the client
driver doesn't update the cached Clob length
[ 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-1a-regression_tests.diff
Attached patch 1a with a small set of regression tests, one of them demonstrates the bug.
The tests are added to jdbcapi.ClobTest.
I also documented a utility method in the test class.
> 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
>
>
> 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.