Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 67657 invoked from network); 10 Feb 2007 16:12:27 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 10 Feb 2007 16:12:27 -0000 Received: (qmail 47468 invoked by uid 500); 10 Feb 2007 16:12:33 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 47428 invoked by uid 500); 10 Feb 2007 16:12:33 -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 47419 invoked by uid 99); 10 Feb 2007 16:12:33 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 10 Feb 2007 08:12:33 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 10 Feb 2007 08:12:25 -0800 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id B10CB7142FB for ; Sat, 10 Feb 2007 08:12:05 -0800 (PST) Message-ID: <16567255.1171123925722.JavaMail.jira@brutus> Date: Sat, 10 Feb 2007 08:12:05 -0800 (PST) From: "Myrna van Lunteren (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Resolved: (DERBY-2301) Documentation of different executeBatch error handling between embedded and DerbyNetClient needed In-Reply-To: <7553785.1170831005504.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/DERBY-2301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Myrna van Lunteren resolved DERBY-2301. --------------------------------------- Resolution: Fixed Fix Version/s: 10.3.0.0 committed with revision 505714. > Documentation of different executeBatch error handling between embedded and DerbyNetClient needed > ------------------------------------------------------------------------------------------------- > > Key: DERBY-2301 > URL: https://issues.apache.org/jira/browse/DERBY-2301 > Project: Derby > Issue Type: Improvement > Components: Documentation > Affects Versions: 10.3.0.0 > Reporter: Myrna van Lunteren > Assigned To: Myrna van Lunteren > Priority: Minor > Fix For: 10.3.0.0 > > Attachments: DERBY-2301.diff > > > There is a difference between embedded and networkserver/DerbyNetClient in how error situations when using java.sql.Statement.executeBatch() and related batch methods are handled. > Embedded 'stops' processing on error, the Client continues. The second mechanism was added as ok behavior with JDBC3.0, I believe, and both are acceptable approaches. > However, it could be disconcerting to an unsuspecting user, seeing as both drivers come from the 'same' codeline, and it should be listed under the differences in the Server and Admin Guide. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.