From sacadmin Fri Aug 21 15:10:30 2009 Received: from sac.sfbay.sun.com (localhost [127.0.0.1]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n7LMAUW3023398; Fri, 21 Aug 2009 15:10:30 -0700 (PDT) Received: (from nw141292@localhost) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8/Submit) id n7LMAU09023394; Fri, 21 Aug 2009 15:10:30 -0700 (PDT) Date: Fri, 21 Aug 2009 15:10:30 -0700 (PDT) From: Nicolas Williams Message-Id: <200908212210.n7LMAU09023394@sac.sfbay.sun.com> To: PSARC-record@sac.sfbay.sun.com Cc: sfwnv-discuss@opensolaris.org Subject: Update SQLite3 to 3.6.17 [PSARC/2009/456 Self Review] Status: RO Content-Length: 564 Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI This information is Copyright 2009 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: Update SQLite3 to 3.6.17 1.2. Name of Document Author/Supplier: Author: Nicolas Williams 1.3 Date of This Document: 21 August, 2009 4. Technical Description See the case directory for more detail 6. Resources and Schedule 6.4. Steering Committee requested information 6.4.1. Consolidation C-team Name: SFW 6.5. ARC review type: Automatic 6.6. ARC Exposure: open From sacadmin Fri Aug 21 15:33:10 2009 Received: from binky.Central.Sun.COM (binky.Central.Sun.COM [129.153.128.104]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n7LMXA0m024831; Fri, 21 Aug 2009 15:33:10 -0700 (PDT) Received: from binky.Central.Sun.COM (localhost [127.0.0.1]) by binky.Central.Sun.COM (8.14.3+Sun/8.14.3) with ESMTP id n7LMMQIh006555; Fri, 21 Aug 2009 17:22:26 -0500 (CDT) Received: (from nw141292@localhost) by binky.Central.Sun.COM (8.14.3+Sun/8.14.3/Submit) id n7LMMQpv006554; Fri, 21 Aug 2009 17:22:26 -0500 (CDT) X-Authentication-Warning: binky.Central.Sun.COM: nw141292 set sender to Nicolas.Williams@sun.com using -f Date: Fri, 21 Aug 2009 17:22:26 -0500 From: Nicolas Williams To: Nicolas Williams Cc: PSARC-record@sac.sfbay.sun.com, sfwnv-discuss@opensolaris.org Subject: Re: Update SQLite3 to 3.6.17 [PSARC/2009/456 Self Review] Message-ID: <20090821222225.GW1043@Sun.COM> References: <200908212210.n7LMAU09023394@sac.sfbay.sun.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200908212210.n7LMAU09023394@sac.sfbay.sun.com> User-Agent: Mutt/1.5.7i Status: RO Content-Length: 1144 I'm filing this self-review case on my own behalf. The update of SQLite3 to 3.6.17 will also enable a heretofore disabled feature: loadable extensions. Loadable extensions are shared objects that can be loaded with sqlite3_load_extension(). See: http://sqlite.org/c3ref/enable_load_extension.html http://sqlite.org/c3ref/load_extension.html The interface stability for these is as for the rest of SQLite3 in Solaris. See PSARC/2008/120. Change history: http://sqlite.org/changes.html The only changes which have any possible interface stability impact are: - The sqlite3_create_function() family of interfaces now return SQLITE_MISUSE instead of SQLITE_ERROR when passed invalid parameter combinations. - When new tables are created using CREATE TABLE ... AS SELECT ... the datatype of the columns is the simplified SQLite datatype (TEXT, INT, REAL, NUMERIC, or BLOB) instead of a copy of the original datatype from the source table. I don't believe these are serious enough even to merit a fasttrack. The latter is a result of the fact that there isn't always a source table in a SQL SELECT statement. Nico --