Re: enabling sqlite by default
| From: | Sterling Hughes | Date: | Mon, 23 Jun 2003 16:48:42 +0000 |
| Subject: | Re: enabling sqlite by default | ||
| References: | 1 2 3 4 5 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-2634@lists.php.net to get a copy of this message | ||
nope, just in cvs. and just as of last night. :) But the footprint of
php5 is actually smaller with regards to sqlite, as the client library
caused more download time.
-Sterling
On Mon, 2003-06-23 at 13:58, Andi Gutmans wrote:
> At 01:12 AM 6/23/2003 -0400, Sterling Hughes wrote:
> >1.5 mb is tiny :)
> >
> >1.5 mb is just a du -ch *.c *.h, and its a one time download. Then you
> >cvs upd the rest of the changes as they happen. As a point of
> >reference, the mbstring extension is 2.9 mb of data, sqlite is in total
> >1.9 mb of data.
> >
> >Libmysql was much more code than the bundled sqlite is. But besides
> >that, I'm talking about enabling by default - not bundling. As I
> >mentioned its been bundled for quite awhile now. :)
>
> It's been bundled in the 4.3.x releases? :) I guess I completely missed
> that part.
>
> Anyway, once it's bundled I am definitely +1 for enabling it by default. I
> didn't know it was bundled (and I'm not talking about CVS but in a release).
>
> Andi
--
"C makes it easy to shoot yourself in the foot; C++ makes it harder,
but when you do, it blows away your whole leg."
- Bjarne Stroustrup