[
https://issues.apache.org/jira/browse/DERBY-6389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kim Haase updated DERBY-6389:
-----------------------------
Attachment: crefjavstateautogen.html
DERBY-6389-2.stat
DERBY-6389-2.diff
Attaching DERBY-6389-2.diff, DERBY-6389-2.stat, and crefjavstateautogen.html,
with these changes:
M src/ref/crefjavstateautogen.dita
D src/adminguide/radminapps811974.dita
I'm removing the "Error message differences" topic, which I'd removed from the
map file but inadvertently left in the workspace.
Please let me know if more fixes to the "Autogenerated keys" topic are needed.
> 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)
