Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 17772 invoked from network); 20 Dec 2006 18:56:47 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 20 Dec 2006 18:56:47 -0000 Received: (qmail 53257 invoked by uid 500); 20 Dec 2006 18:56:52 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 53223 invoked by uid 500); 20 Dec 2006 18:56:52 -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 53207 invoked by uid 99); 20 Dec 2006 18:56:52 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 Dec 2006 10:56:52 -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; Wed, 20 Dec 2006 10:56:42 -0800 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 885847142A1 for ; Wed, 20 Dec 2006 10:56:22 -0800 (PST) Message-ID: <25336802.1166640982555.JavaMail.jira@brutus> Date: Wed, 20 Dec 2006 10:56:22 -0800 (PST) From: =?utf-8?Q?=C3=98ystein_Gr=C3=B8vlen_=28JIRA=29?= To: derby-dev@db.apache.org Subject: [jira] Commented: (DERBY-208) Add support to retrieve lobs for Network Server by locator rather than matierializing the LOB In-Reply-To: <1275007121.1113178756447.JavaMail.jira@ajax.apache.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org [ http://issues.apache.org/jira/browse/DERBY-208?page=3Dcomments#action= _12460017 ]=20 =20 =C3=98ystein Gr=C3=B8vlen commented on DERBY-208: --------------------------------------- Great work with the thorough use-cases, Fernanda. =20 I suggest to go for an implementations where locators work on copies and no= t directly on the LOBs. Working directly on a LOB can change the behavior = of current applications since updates may occur without a call to updateRow= (). Hence, applications which sets parameters and then for some reason ski= ps updateRow(), will experience a changed behavior. Also, it seems like th= e infrastructure for working on a copy will be needed anyway in order to te= mporarily store LOBs that have not yet been assigned to a row. > Add support to retrieve lobs for Network Server by locator rather than ma= tierializing the LOB > -------------------------------------------------------------------------= -------------------- > > Key: DERBY-208 > URL: http://issues.apache.org/jira/browse/DERBY-208 > Project: Derby > Issue Type: New Feature > Components: Network Server > Affects Versions: 10.1.1.0 > Reporter: Kathey Marsden > Attachments: LOBLocator.pdf > > > Currently Network Server materializes all LOB objects. LOB locator suppo= rt is part of the DRDA spec so could be added to network server. See > http://www.opengroup.org/dbiop/ > It is not clear if SQL Support for LOB locators would also be required. --=20 This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: htt= p://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira