Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 18220 invoked from network); 4 Jun 2007 13:01:02 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 4 Jun 2007 13:01:02 -0000 Received: (qmail 98105 invoked by uid 500); 4 Jun 2007 13:01:04 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 98045 invoked by uid 500); 4 Jun 2007 13:01:03 -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 97996 invoked by uid 99); 4 Jun 2007 13:01:03 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Jun 2007 06:01:03 -0700 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED 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; Mon, 04 Jun 2007 06:00:58 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id C37584297CC for ; Mon, 4 Jun 2007 06:00:37 -0700 (PDT) Message-ID: <1291813.1180962037757.JavaMail.jira@brutus> Date: Mon, 4 Jun 2007 06:00:37 -0700 (PDT) From: "Knut Anders Hatlen (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Updated: (DERBY-2604) Implement Clob support for locators In-Reply-To: <573529.1178195715363.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-2604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Knut Anders Hatlen updated DERBY-2604: -------------------------------------- Derby Info: (was: [Patch Available]) Looks good to me. Committed revision 544119. A couple of minor nits: The new field maxPos in ClobLocatorInputStream/Reader could be final, I think. (The same is probably true for the clob and connection field, and for the corresponding fields in the Blob streams, but those classes/fields were not touched by your patch.) Since there are both JDBC positions (counting from 1) and stream positions (counting from 0) in the stream classes, it would be good if maxPos's javadoc said where maxPos started counting from. In Clob.positionX(), I think that it would be clearer if the code that increments index by 1 for non-locator lobs were moved into the else block right above it. (Then we don't need to check isLocator() twice.) Also in Clob.positionX(), I think the index variable should be changed to a long. As it is now, clobGetPositionFromLocator() returns a long which is cast to int before it is cast back to long and returned. It's better to keep it as a long all the way. > Implement Clob support for locators > ----------------------------------- > > Key: DERBY-2604 > URL: https://issues.apache.org/jira/browse/DERBY-2604 > Project: Derby > Issue Type: Sub-task > Components: Network Server > Reporter: V.Narayanan > Assignee: V.Narayanan > Fix For: 10.3.0.0 > > Attachments: ClobLocatorWork_v1.diff, ClobLocatorWork_v1.stat, ClobLocatorWork_v2.diff, ClobLocatorWork_v2.stat, ClobLocatorWork_v3.diff, ClobLocatorWork_v3.stat, ClobLocatorWork_v4.diff, ClobLocatorWork_v4.stat, ClobLocatorWork_v5.diff, ClobLocatorWork_v5.stat, ConnectionLocatorWork_v2.diff, ConnectionLocatorWork_v4.diff > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.