Re: [Phpwiki-talk] Re: MySQL PHP rift

[Reini U. <ru...@x-...>]

Whit Blauvelt schrieb:
> On Thu, Mar 18, 2004 at 11:56:13AM +1100, Matthew Palmer wrote:
>>To their credit, MySQL have been fairly public in their attempts to sort the
>>problems out, and it would be an incredible shame if this didn't go well in
>>the long run, because MySQL have been, in a way, the posterchild for the
>>"you can GPL your software AND make money!" argument 
> 
> Amen. MySQL is good stuff and good people. A few years back when I had an
> obscure bug to complain of (in a charitable situation where there were no
> bucks to be sending their way) I got full attention from the main man there.
> 
> As for PHP, I've been using it since Rasmus jumped into a newsgroup
> discussion about a commercial Web-scripting product back in '93 to point out
> he was giving something better away free. The current PHP powers have lost
> the a bit of the spirit of generousity and inclusion the language began from
> - which is especially tacky considering how much of PHP's usefulness has
> come from it's facility with MySQL. I'm all for purity; but I'm also for
> remembering who your true friends have been.
> 
> Is there consideration of depricating MySQL support in PhpWiki, or just
> expanding other options?

For sure not in PhpWiki.
But I'm deeply concerned about PHP's decision during the last year, 
dropping the libmysqlclient from PHP core and enforcing SQLite as 
default DB (MySQL replacement) in core. From php-5.x on libmysql is just 
a module.

Well, SQLite is faster, has the server included, is therefore much 
easier to install and has almost the same features as MySQL.
But: There's no SQLite module for the older PHP's!
So we cannot enforce SQLite as default dbtype to replace dbm, though it 
would make sense since SQLite is now in core and the various dbm libs 
only as module. And windows has other default dbm backends than unix.
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/