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:02:44 UTC
[jira] Created: (DERBY-3978) Clob.truncate(long) in the client
driver doesn't update the cached Clob length
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.4.2.0, 10.3.3.0, 10.5.0.0
Reporter: Kristian Waagan
Assignee: Kristian Waagan
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.
[jira] Resolved: (DERBY-3978) Clob.truncate(long) in the client
driver doesn't update the cached Clob length
Posted by "Kristian Waagan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Waagan resolved DERBY-3978.
------------------------------------
Resolution: Fixed
Fix Version/s: 10.3.3.1
Regression tests on the 10.3 branch ran successfully.
Backported with revision 725662.
This concludes the work on this issue. Awaiting confirmation from test runs before closing.
> 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
> Fix For: 10.3.3.1, 10.4.2.1, 10.5.0.0
>
> 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.
[jira] Updated: (DERBY-3978) Clob.truncate(long) in the client
driver doesn't update the cached Clob length
Posted by "Kristian Waagan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Waagan updated DERBY-3978:
-----------------------------------
Fix Version/s: 10.4.2.1
Backported patches 1a and 2a to the 10.4 branch with revision 725620. Regressions tests ran cleanly.
Merge to 10.3 was also clean, running tests now.
> 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
> Fix For: 10.4.2.1, 10.5.0.0
>
> 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.
[jira] Updated: (DERBY-3978) Clob.truncate(long) in the client
driver doesn't update the cached Clob length
Posted by "Kristian Waagan (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Closed: (DERBY-3978) Clob.truncate(long) in the client
driver doesn't update the cached Clob length
Posted by "Kristian Waagan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Waagan closed DERBY-3978.
----------------------------------
No problems reported. Closing the issue.
> 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
> Fix For: 10.3.3.1, 10.4.2.1, 10.5.0.0
>
> 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.
[jira] Updated: (DERBY-3978) Clob.truncate(long) in the client
driver doesn't update the cached Clob length
Posted by "Kristian Waagan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Waagan updated DERBY-3978:
-----------------------------------
Derby Info: (was: [Patch Available])
Fix Version/s: 10.5.0.0
Regression tests ran without failures.
Committed patches 1a and 2a to trunk with revision 724657.
Awaiting test results and community feedback before I backport the changes.
> 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
> Fix For: 10.5.0.0
>
> 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.
[jira] Updated: (DERBY-3978) Clob.truncate(long) in the client
driver doesn't update the cached Clob length
Posted by "Kristian Waagan (JIRA)" <ji...@apache.org>.
[ 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.