Re: enabling everything by default
| From: | Scott MacVicar | Date: | Fri, 01 Aug 2008 10:41:26 +0000 |
| Subject: | Re: enabling everything by default | ||
| References: | 1 2 3 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-39528@lists.php.net to get a copy of this message | ||
Antony Dovgal wrote:
On 01.08.2008 14:20, Scott MacVicar wrote: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.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?
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. ScottIf 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.