But my argument is that NOTHING should be enabled "by default" unless it
already has connection libraries. Including a static (i.e. not updated
when postgresql gets updated) connection library is a bad thing, since any
bug in the connection lib will live on in the staticly linked connection
code shipped with PHP.
If the connection libs for DB2, Oracle, and Postgresql are found on the
machine, then PHP should autoconfigure to use them. If they're not there,
then including them in the php distro is short sighted and likely to cause
as many problems as it fixes.
Keep in mind that including the MySQL libs with PHP was a mixed bag, since
using a different mysql connect lib for PHP and another for apache if you
use mod_auth_mysql would result in a crashing server situation that was
suboptimal.
Rather than include ANY interface, I think it would be wiser to only use
the connect libs that are already on a server. I got the feeling Sterling
agreed with me on that point, by the way.
On 24 Jun 2003, Robert Treat wrote:
> On Tue, 2003-06-24 at 03:47, Christopher Kings-Lynne wrote:
> > > I'm trying to say (badly) that we'd like postgres by default.
> >
> > Yes, but I think we'd have more luck asking for 'level playing field'. That
> > fair to everyone then, otherwise we just become the next MySQL!
> >
>
> yes, but they are talking are already about switching from mysql to
> sqlite. if they are going to switch to *something* i see no reason not
> to lobby that they switch to postgresql. the problem with mysql arose
> from them switching their libraries to gpl licensing (which forces
> people to either use gpl or buy a license from mysql), we're never going
> to do that, so php never has to worry about that.
>
> imo sqlite is a "step back" from mysql as far as capabilities go; i
> think many of their users would rather have a "step forward", and
> postgresql can offer that.
>
> Robert Treat
> --
> Build A Better Lamp :: Linux Apache {middleware} PostgreSQL
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org
>