db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Øystein Grøvlen (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 Fri, 13 Jul 2007 06:47:04 GMT

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

Øystein Grøvlen commented on DERBY-2932:
----------------------------------------

Narayanan, your explanation makes sense.  I agree that these errors are to be expected.  This
change in behavior is explained in the release note on the locator-based implementation.

As I said, the patch looks good and I have tested that it solves the described problem.
+1 to commit.


> 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.2
>
>         Attachments: SoftUpgrade_createClob_createBlob_v1.diff, SoftUpgrade_createClob_createBlob_v1.stat
>
>


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