Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:38696 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 23875 invoked from network); 2 Jul 2008 00:13:09 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 2 Jul 2008 00:13:09 -0000 Authentication-Results: pb1.pair.com header.from=scott@macvicar.net; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=scott@macvicar.net; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain macvicar.net from 193.227.246.108 cause and error) X-PHP-List-Original-Sender: scott@macvicar.net X-Host-Fingerprint: 193.227.246.108 ip246-108-v193.static.x-ip.net Received: from [193.227.246.108] ([193.227.246.108:33928] helo=lovelace.midden.org.uk) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id A3/02-10269-218CA684 for ; Tue, 01 Jul 2008 20:13:07 -0400 Received: from macvicar.demon.co.uk ([80.177.111.173] helo=[192.168.1.101]) by lovelace.midden.org.uk with esmtpsa (TLS-1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.69) (envelope-from ) id 1KDq0r-000752-CG for internals@lists.php.net; Wed, 02 Jul 2008 01:15:59 +0100 Message-ID: <1FF452D5-E404-4B86-BA86-E0712F54A03E@macvicar.net> To: internals Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v926) Date: Wed, 2 Jul 2008 01:12:55 +0100 X-Mailer: Apple Mail (2.926) X-Spam-Score: -4.0 X-Spam_Report: Spam detection software, running on the system "lovelace.midden.org.uk", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: Hi All, I've been working on sqlite3[1] as a replacement for the ageing sqlite extension, I've had a few people interested in getting this into 5.3 and I think its definitely a possibility as the API is more or less finalised at this moment in time. [...] Content analysis details: (-4.0 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.8 ALL_TRUSTED Passed through trusted hosts only via SMTP -2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1% [score: 0.0000] 0.4 AWL AWL: From: address is in the auto white-list Subject: SQLite3 From: scott@macvicar.net (Scott MacVicar) Hi All, I've been working on sqlite3[1] as a replacement for the ageing sqlite extension, I've had a few people interested in getting this into 5.3 and I think its definitely a possibility as the API is more or less finalised at this moment in time. The reason that the current sqlite extension can't be modified is due to the libsqlite API changes, they just aren't compatible in any shape or form, they also use a different database format which would probably add to the confusion since this format isn't backwards compatible. At the moment the only things left on my todo would be documentation and buffered queries. I'd appreciate any feedback or comments about adding this. Scott [1] http://pecl.php.net/sqlite3