db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kim Haase (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-6389) Update adminguide's list of differences between client and embedded
Date Tue, 29 Oct 2013 14:00:31 GMT

    [ https://issues.apache.org/jira/browse/DERBY-6389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13807996#comment-13807996

Kim Haase commented on DERBY-6389:

Thanks for all the information!

I ran the ij commands in your comment about the updatable result sets topic and found that
although they all ran fine in a client environment, there were failures in the embedded environment
here (after the "next c" line):

ij> update t set c11 = 4 where current of c;
ERROR 24000: Invalid cursor state - no current row.
ij> update t set y = 4 where current of c;
ERROR 42X30: Cursor 'C' not found. Verify that autocommit is off.

Do these qualify under the "Error messages and SQLStates can differ between the network client
and embedded driver" statement, or could something more specific be said?
Are these described

> Update adminguide's list of differences between client and embedded
> -------------------------------------------------------------------
>                 Key: DERBY-6389
>                 URL: https://issues.apache.org/jira/browse/DERBY-6389
>             Project: Derby
>          Issue Type: Bug
>          Components: Documentation
>            Reporter: Knut Anders Hatlen
>            Assignee: Kim Haase
> The admin guide has a chapter that describes known differences between the client driver
and the embedded driver: http://db.apache.org/derby/docs/10.10/adminguide/cadminapps.html
> Most of this information was added for the original network client implementation in
10.1 (DERBY-371) and has not been updated since.
> For example, http://db.apache.org/derby/docs/10.10/adminguide/cadminappsclientdiffs.html
says SQLStates for exceptions on the client may be null. I believe this was fixed in 10.2
as part of DERBY-254.
> It also says that SQLExceptions (and SQLWarnings) won't be chained, but that was fixed
in 10.3 (DERBY-2692). That outdated information is also repeated here: http://db.apache.org/derby/docs/10.10/adminguide/radminapps811974.html

This message was sent by Atlassian JIRA

View raw message