Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 98846 invoked from network); 17 Aug 2009 20:59:33 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 17 Aug 2009 20:59:33 -0000 Received: (qmail 22659 invoked by uid 500); 17 Aug 2009 20:59:39 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 22634 invoked by uid 500); 17 Aug 2009 20:59:39 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 22626 invoked by uid 99); 17 Aug 2009 20:59:39 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 Aug 2009 20:59:39 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 Aug 2009 20:59:36 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id E892C29A0011 for ; Mon, 17 Aug 2009 13:59:14 -0700 (PDT) Message-ID: <1882946825.1250542754951.JavaMail.jira@brutus> Date: Mon, 17 Aug 2009 13:59:14 -0700 (PDT) From: "Dag H. Wanvik (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Updated: (DERBY-310) Document and/or change Derby client code to match behavior with Embedded driver where possible. In-Reply-To: <1257613302.1116879775287.JavaMail.jira@ajax.apache.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/DERBY-310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dag H. Wanvik updated DERBY-310: -------------------------------- 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 was: 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 > 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 > > [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 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.