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

ASF subversion and git services commented on DERBY-6389:
--------------------------------------------------------

Commit 1537251 from [~chaase3] in branch 'docs/trunk'
[ https://svn.apache.org/r1537251 ]

DERBY-6389  Update adminguide's list of differences between client and embedded

Deleted an Admin Guide topic, modified a Reference Manual topic.

Patch: DERBY-6389-2.diff

> 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, ClientExample.java, 
> crefjavstateautogen.html, DERBY-6389-2.diff, DERBY-6389-2.stat, 
> DERBY-6389.diff, DERBY-6389.stat, DERBY-6389.zip, DERBY-6389.zip, 
> EmbeddedExample.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)

Reply via email to