db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "V.Narayanan (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-2932) Connection.createClob() and Connection.createBlob() throw a procedure not found exception and do not switch to non-locator code upon soft upgrade
Date Thu, 12 Jul 2007 14:10:04 GMT

    [ https://issues.apache.org/jira/browse/DERBY-2932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12512102
] 

V.Narayanan commented on DERBY-2932:
------------------------------------

The problem can be reproduced with the following series of steps

1. Create a database with 10.2, and disconnect.
2. Start a 10.3 server.
3. get a connection and call createClob() or createBlob() methods on the
    connection interface.

SYSIBM.BLOBCREATELOCATOR is not recognized as a function or procedure 
is thrown upon createBlob and 

SYSIBM.CLOBCREATELOCATOR is not recognized as a function or procedure
is thrown upon doing a createClob

> Connection.createClob() and Connection.createBlob() throw a procedure not found exception
and do not switch to non-locator code upon soft upgrade
> -------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-2932
>                 URL: https://issues.apache.org/jira/browse/DERBY-2932
>             Project: Derby
>          Issue Type: Bug
>          Components: Network Client
>    Affects Versions: 10.3.0.0, 10.3.1.0, 10.3.1.1
>            Reporter: V.Narayanan
>            Assignee: V.Narayanan
>            Priority: Blocker
>             Fix For: 10.3.1.1
>
>


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