[
https://issues.apache.org/jira/browse/DERBY-310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12707107#action_12707107
]
Kathey Marsden commented on DERBY-310:
--------------------------------------
I think now that we have the client/embedded differences checkbox, we should
just verify that the linked issues have the box checked and close this issue.
Does that sound ok?
> Document and/or change Derby client code to match behavior with Embedded
> driver where possible.
> -----------------------------------------------------------------------------------------------
>
> Key: DERBY-310
> URL: https://issues.apache.org/jira/browse/DERBY-310
> Project: Derby
> Issue Type: Improvement
> Components: Documentation, JDBC
> Affects Versions: 10.1.1.0
> Reporter: Satheesh Bandaram
> Priority: Minor
>
> There are some behavior differences between Derby client and embedded JDBC
> drivers. Change Derby client code to match embedded behavior or document some
> of these differences.
> This JIRA entry is a top level task for tracking these issues. Individual
> subtasks should be created or existing tasks linked to this Jira entry, but
> no specific feature content added here. Please create subtaks to this Jira
> entry to track any known differences documentation issues or tasks needed to
> investigate this issue.
> Kathey Marsden also started this effort to compile known
> differences.(http://mail-archives.apache.org/mod_mbox/db-derby-dev/200505.mbox/%[email protected]%3e)
> The Derby community voted that client should match embedded where possible.
> See:
> http://mail-archives.apache.org/mod_mbox/db-derby-dev/200505.mbox/%[email protected]%3e
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
