[
https://issues.apache.org/jira/browse/DERBY-3658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12593842#action_12593842
]
Knut Anders Hatlen commented on DERBY-3658:
-------------------------------------------
Thanks for looking at the patch, Kristian. The tests passed, so I committed the
patch to trunk with revision 652865. I also plan to back-port it to the 10.4
branch. I'll also see if I can clarify the comments for [Net]Cursor.locator().
> LOBStateTracker should not use SYSIBM.CLOBRELEASELOCATOR when the database is
> soft-upgraded from 10.2
> -----------------------------------------------------------------------------------------------------
>
> Key: DERBY-3658
> URL: https://issues.apache.org/jira/browse/DERBY-3658
> Project: Derby
> Issue Type: Bug
> Components: JDBC, Network Client
> Affects Versions: 10.4.1.3
> Reporter: Knut Anders Hatlen
> Assignee: Knut Anders Hatlen
> Priority: Minor
> Attachments: d3658.diff
>
>
> Reported by Daniel Noll on derby-user:
> http://thread.gmane.org/gmane.comp.apache.db.derby.user/9107
> To reproduce:
> 1. Create a database with Derby 10.2.2.0
> 2. Create a table with a clob column and insert some data
> 3. Access that database with client+server at version 10.4.1.3 and iterate
> through the rows in the table
> You'll see an error message like this:
> ERROR 42Y03: 'SYSIBM.CLOBRELEASELOCATOR' is not recognized as a function or
> procedure.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
