db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-3658) LOBStateTracker should not use SYSIBM.CLOBRELEASELOCATOR when the database is soft-upgraded from 10.2
Date Fri, 02 May 2008 21:04:55 GMT

     [ https://issues.apache.org/jira/browse/DERBY-3658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Knut Anders Hatlen updated DERBY-3658:
--------------------------------------

    Affects Version/s: 10.3.2.2

Yes, I'll do that. I didn't think the bug affected 10.3, but it seems like LOBStateTracker
is present on the 10.3 branch as well. Added 10.3.2.2 to the list of affected versions.

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


Mime
View raw message