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 15:50:30 GMT

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

Kim Haase commented on DERBY-6389:
----------------------------------

Here's another oddity, concerning "Differences in JDBC 3.0 methods" (http://db.apache.org/derby/docs/10.10/adminguide/cadminappsjdbcdiffs.html).
When I tried to run the Statement.execute(String sql, String[] columnNames) and Statement.execute(String
sql, int[] columnIndexes) methods, they appeared to work fine with the client driver but to
fail with the embedded driver -- the opposite behavior from what is described. The error is
"SQLException: Table 'T1' does not have an auto-generated column named 'a'." Any ideas? I
can attach my examples.


> 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
>         Attachments: ClientExample.java, EmbeddedExample.java
>
>
> 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
(v6.1#6144)

Mime
View raw message