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 "Knut Anders Hatlen (JIRA)" <ji...@apache.org> on 2008/05/03 00:18:56 UTC
[jira] Resolved: (DERBY-3658) LOBStateTracker should not use
SYSIBM.CLOBRELEASELOCATOR when the database is soft-upgraded from 10.2
[ https://issues.apache.org/jira/browse/DERBY-3658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Knut Anders Hatlen resolved DERBY-3658.
---------------------------------------
Resolution: Fixed
I updated the comments in Connection.serverSupportsLocators() and Cursor.locator() so that they say explicitly that a server that supports locators may send LOB values instead of locators if the database is soft upgraded. Committed (to trunk only) revision 652929.
> 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.3.2.2, 10.4.1.3
> Reporter: Knut Anders Hatlen
> Assignee: Knut Anders Hatlen
> Priority: Minor
> Fix For: 10.3.2.2, 10.4.1.4, 10.5.0.0
>
> 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.