Derby
  1. Derby
  2. DERBY-310

Document and/or change Derby client code to match behavior with Embedded driver where possible.

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 10.6.1.0
    • Fix Version/s: 10.6.1.0
    • Component/s: Documentation, JDBC
    • Labels:
      None

      Description

      [NOTE: This meta-issue has been replaced by the "Bug behavior facts" flag "Embedded/client difference" DagW 2009-08-17]

      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/%3c42854697.1090403@sbcglobal.net%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/%3c4298CDDE.5070305@sbcglobal.net%3e

        Issue Links

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              Satheesh Bandaram
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development