Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 81859 invoked from network); 21 Apr 2009 15:32:22 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 21 Apr 2009 15:32:22 -0000 Received: (qmail 76877 invoked by uid 500); 21 Apr 2009 15:32:19 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 76841 invoked by uid 500); 21 Apr 2009 15:32:19 -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 76833 invoked by uid 99); 21 Apr 2009 15:32:19 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 21 Apr 2009 15:32:19 +0000 X-ASF-Spam-Status: No, hits=-4.0 required=10.0 tests=RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [192.18.43.132] (HELO sca-es-mail-1.sun.com) (192.18.43.132) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 21 Apr 2009 15:32:09 +0000 Received: from fe-sfbay-09.sun.com ([192.18.43.129]) by sca-es-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id n3LFVZYh008750 for ; Tue, 21 Apr 2009 08:31:48 -0700 (PDT) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; format=flowed; charset=ISO-8859-1 Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009)) id <0KIG00D00J4J0300@fe-sfbay-09.sun.com> for derby-dev@db.apache.org; Tue, 21 Apr 2009 08:31:35 -0700 (PDT) Received: from richard-hillegas-computer.local ([unknown] [129.150.16.143]) by fe-sfbay-09.sun.com (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009)) with ESMTPSA id <0KIG000FLJ4NNEB0@fe-sfbay-09.sun.com> for derby-dev@db.apache.org; Tue, 21 Apr 2009 08:31:35 -0700 (PDT) Date: Tue, 21 Apr 2009 08:31:35 -0700 From: Rick Hillegas Subject: Re: Stored Prepared Statements? -- Thoughts on exposing StorablePreparedStatements to user/external statements In-reply-to: <49EDC532.2030607@sun.com> Sender: Richard.Hillegas@Sun.COM To: derby-dev@db.apache.org Message-id: <49EDE6D7.2090805@sun.com> References: <157681730964895697200108835802389536937-Webmail@me.com> <143927183394444463994628353627913852529-Webmail@me.com> <49ECFBC6.1000002@sbcglobal.net> <49EDC532.2030607@sun.com> User-Agent: Thunderbird 2.0.0.21 (Macintosh/20090302) X-Virus-Checked: Checked by ClamAV on apache.org In order to persist ordinary user statements, we will need to think carefully about every bit of compiled state which was added to executable statements after cloudscape removed support for storing user statements. For instance, I believe that when GRANT/REVOKE was added, there was no need to persist the compiled list of required permissions. I don't see this list being persisted in GenericStorablePreparedStatement.writeExternal(). Regards, -Rick