Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:39528
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain macvicar.net from 193.227.246.108 cause and error)
Message-ID: <4892E856.6090108@macvicar.net>
Date: Fri, 01 Aug 2008 11:41:26 +0100
User-Agent: Thunderbird 2.0.0.16 (Windows/20080708)
MIME-Version: 1.0
To: Antony Dovgal <tony@daylessday.org>
CC: php-dev <internals@lists.php.net>
References: <4892E15D.1080004@daylessday.org> <4892E37B.8060804@macvicar.net> <4892E5DD.50907@daylessday.org>
In-Reply-To: <4892E5DD.50907@daylessday.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
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:  Antony Dovgal wrote: > On 01.08.2008 14:20, Scott MacVicar
	wrote: >> ext/pdo_sqlite and ext/sqlite3 use the same underlying lib so its
	just >> another wrapper but without the PDO crap on top. > > I know, I know.
	> But why enable it by default (as well as PDO_SQLITE)? What's so > extremely
	useful in this extension that every user needs it? [...] 
	Content analysis details:   (-4.3 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.1 AWL                    AWL: From: address is in the auto white-list
Subject: Re: [PHP-DEV] enabling everything by default
From: scott@macvicar.net (Scott MacVicar)

Antony Dovgal wrote:
> On 01.08.2008 14:20, Scott MacVicar wrote:
>> ext/pdo_sqlite and ext/sqlite3 use the same underlying lib so its just 
>> another wrapper but without the PDO crap on top.
> 
> I know, I know.
> But why enable it by default (as well as PDO_SQLITE)? What's so 
> extremely useful in this extension that every user needs it?

The zero configuration aspect, the ability to just throw up a database 
in place of your own over complicated storage format. Sure all hosts 
have MySQL but if you're shipping a product then sometimes its simpler 
to just bundle a SQLite DB.

Clientside apps are also moving forward with SQLite, Firefox 3.0, Google 
Gears, Adobe AIR and just about every Apple product. I've been writing 
PHP scripts to start using the data.

I'm happy to disable PDO by default and have you force it on like mysql 
or any of the others.

> 
>> If you have ideas on testing without enabling them or bundling in the 
>> build please do share. It's a chicken and egg situtation imho.
> 
> Testing doesn't require enabling it by default.
> In fact, it doesn't even require putting the extension in the core, 
> though this surely increases the the amount of feedback.
> Developers should test their extensions, not users.
> 

Yep, we're already using it here in several applications and I have a 
few side projects using it.

Test coverage was good, about 80%. I'll be doing more before alpha 2.

Scott