Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 35884 invoked from network); 18 Jun 2005 19:59:43 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 18 Jun 2005 19:59:43 -0000 Received: (qmail 52442 invoked by uid 500); 18 Jun 2005 19:59:42 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 52410 invoked by uid 500); 18 Jun 2005 19:59:42 -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: "Derby Development" Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 52395 invoked by uid 99); 18 Jun 2005 19:59:42 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from ajax-1.apache.org (HELO ajax.apache.org) (192.87.106.226) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 18 Jun 2005 12:59:37 -0700 Received: from ajax.apache.org (ajax.apache.org [127.0.0.1]) by ajax.apache.org (Postfix) with ESMTP id C76C514 for ; Sat, 18 Jun 2005 21:59:17 +0200 (CEST) Message-ID: <1043317068.1119124757815.JavaMail.jira@ajax.apache.org> Date: Sat, 18 Jun 2005 21:59:17 +0200 (CEST) From: "Jeff Levitt (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Updated: (DERBY-370) Document differences between Embedded and Network Server for Updatable ResultSets functionality In-Reply-To: <1910153505.1119031256694.JavaMail.jira@ajax.apache.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ http://issues.apache.org/jira/browse/DERBY-370?page=all ] Jeff Levitt updated DERBY-370: ------------------------------ Attachment: derby370revised.zip All set Mamta, the attached patch capitalizes "Result Sets" in the title. Please let me know if it looks good now. Thanks! > Document differences between Embedded and Network Server for Updatable ResultSets functionality > ----------------------------------------------------------------------------------------------- > > Key: DERBY-370 > URL: http://issues.apache.org/jira/browse/DERBY-370 > Project: Derby > Type: Sub-task > Components: Documentation > Versions: 10.1.1.0 > Reporter: Mamta A. Satoor > Assignee: Jeff Levitt > Fix For: 10.1.1.0 > Attachments: derby370revised.zip > > The functionality of updatable resultset for Network Server is similar to what Embedded Derby supports, with the exception of following differences > 1)DNC requires that there be at least one column in the select list from the target table. > eg select 1, 2 from t1 for update of c11 will fail in Network Server because driver looks at both the columns in the select list and it can't determine the target table for update/delete looking at those columns' metadata. This is not required by embedded driver. There is test for this (Positive Test2 in updatableResultSet.java). > 2)Embedded driver allows Statement name change when there is an open resultset on that statement object. DNC driver does not supported that. (Positive Test8a and Test8b in updatableResultSet.java ) > 3)(Positive Test20) Embedded driver allows updateString on SMALLINT, INTEGER, BIGINT, DECIMAL datatypes. DNC doesn't. > Embedded driver support updateBytes on CHAR, VARCHAR, LONG VARCHAR datatypes. DNC doesn't > Embedded driver support updateTime on TIMESTAMP datatypes. DNC doesn't > Embedded driver supports updateObject with null value. DNC doesn't > DNC does not support updateClob and updateBlob -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira