Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 42131 invoked from network); 17 Jan 2005 22:56:19 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 17 Jan 2005 22:56:19 -0000 Received: (qmail 32123 invoked by uid 500); 17 Jan 2005 22:56:18 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 32092 invoked by uid 500); 17 Jan 2005 22:56:18 -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 32079 invoked by uid 99); 17 Jan 2005 22:56:17 -0000 X-ASF-Spam-Status: No, hits=0.3 required=10.0 tests=FORGED_RCVD_HELO,HTML_10_20,HTML_MESSAGE X-Spam-Check-By: apache.org Received-SPF: neutral (hermes.apache.org: local policy) Received: from e2.ny.us.ibm.com (HELO e2.ny.us.ibm.com) (32.97.182.142) by apache.org (qpsmtpd/0.28) with ESMTP; Mon, 17 Jan 2005 14:56:16 -0800 Received: from d01relay04.pok.ibm.com (d01relay04.pok.ibm.com [9.56.227.236]) by e2.ny.us.ibm.com (8.12.10/8.12.10) with ESMTP id j0HMuESK003627 for ; Mon, 17 Jan 2005 17:56:14 -0500 Received: from d01av02.pok.ibm.com (d01av02.pok.ibm.com [9.56.224.216]) by d01relay04.pok.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id j0HMuEfE142286 for ; Mon, 17 Jan 2005 17:56:14 -0500 Received: from d01av02.pok.ibm.com (loopback [127.0.0.1]) by d01av02.pok.ibm.com (8.12.11/8.12.11) with ESMTP id j0HMuErA027896 for ; Mon, 17 Jan 2005 17:56:14 -0500 Received: from Remulak.Net (sig-9-48-113-240.mts.ibm.com [9.48.113.240]) by d01av02.pok.ibm.com (8.12.11/8.12.11) with ESMTP id j0HMuDPg027887 for ; Mon, 17 Jan 2005 17:56:13 -0500 Message-ID: <41EC421B.47D3DDBB@Remulak.Net> Date: Mon, 17 Jan 2005 14:54:19 -0800 From: Mamta Satoor X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Derby Development Subject: Changes to Derby JDBC Implementation Notes page References: <41EC0242.1080900@golux.com> Content-Type: multipart/alternative; boundary="------------60C4E09203AC3839E4CCFCEB" X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N --------------60C4E09203AC3839E4CCFCEB Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi, Thanks to Dan for commiting my changes for updatable resultsets over the weekend. I think this is a good time to update the Derby JDBC Implementation Notes page for updatable resultsets. I will appreciate if one of the committers can add following 2 paragraphs. Following should go in the doc right before the java.sql.ResultSet section Java.sql.Connection CreateStatement, prepareStatement and prepareCall Behavior Clarification CONCUR_UPDATABLE concurrency is supported for FORWARD ONLY ResultSet types only. Following should go in the doc in the java.sql.ResultSet section before the getAsciiStream() api deleteRow() Behavior Clarification After deleteRow, ResultSet will be positioned right before the next row for FORWARD ONLY updatable ResultSets. thanks, Mamta --------------60C4E09203AC3839E4CCFCEB Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit Hi,

Thanks to Dan for commiting my changes for updatable resultsets over the weekend.
I think this is a good time to update the Derby JDBC Implementation Notes page
for updatable resultsets. I will appreciate if one of the committers can add following
2 paragraphs.

Following should go in the doc right before the java.sql.ResultSet section
Java.sql.Connection

CreateStatement, prepareStatement and prepareCall

Behavior Clarification

CONCUR_UPDATABLE concurrency is supported for FORWARD ONLY ResultSet types only.

Following should go in the doc in the java.sql.ResultSet section before the getAsciiStream() api

deleteRow()

Behavior Clarification

After deleteRow, ResultSet will be positioned right before the next row for FORWARD ONLY updatable ResultSets.

thanks,
Mamta --------------60C4E09203AC3839E4CCFCEB--