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/05/02 15:46:55 UTC

[jira] Commented: (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:comment-tabpanel&focusedCommentId=12593786#action_12593786 ] 

Kristian Waagan commented on DERBY-3658:
----------------------------------------

The approach taken seems sound. +1 to commit if the tests pass.

I missed the point when I implemented this, believing if the server supported locators Cursor.locator would return a valid locator.
Does it make sense to explicitly note the possibility of an invalid locator even if the server supports it, for instance in [Net]Cursor.locator?
That said, the possibility of getting INVALID_LOCATOR should of course have made me check the value...

> 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.