Tim Parkin wrote: > > [...] I agree that SQLite is a good idea, however I also > see the need for standard, > bundled db client code, after all the MySQL inclusion has had an > enormous impact on hosting > and hence the direction of mine and many other PHP oriented > industries. > The real question is: why is (was) the mysql client lib bundled?
Most hosting companies (I know of) use either (a) self compiled or (b) SuSE/Redhat/Debian based PHP modules. (a) would be less a problem - these folks know what they're doing (b) At least SuSE and Debian do not use the bundled mysql client. Also their pkg maint's know what they're doing, and already have proven ./configure's to enable most modules - either compiled-in or through dynamic loading. If I were them, I would also enable sqlite once I know of that ext, either through word of mouth, or direct mailing from one of the core PHP folks. (If this is not done already, some kind of communication channel should be established to the pkg mnt's from the major distros) IMHO, PHP compiles and runs fine w/o the bundled mysql client. Again, I don't know why it was bundled once a day, so from today's point of view, I don't see arguments to keep it bundled. Also, I totally agree with Rasmus and Sterling, that bundling sqlite is a Good Thing(tm), for all the reasons they mentioned. I'm against enabling it by default, all it's pros and cons have to be promoted to the distros (and hosting companies), to get it enabled by _them_. My 2c, Thomas -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
