On Mon, 23 Jun 2003, Reuben D. Budiardja wrote:
> On Sunday 22 June 2003 11:22 pm, Alvaro Herrera wrote:
> > On Sun, Jun 22, 2003 at 10:19:20PM -0400, Tom Lane wrote:
> > > Bruce Momjian <pgman@candle.pha.pa.us> writes:
> > > > Interesting thread (php-dev subj: removing bundled libmysql):
> > > > http://marc.theaimsgroup.com/?l=php-dev&m=105621066832429&w=2
> >
> > Note the comment on
> > http://marc.theaimsgroup.com/?l=php-dev&m=105624024116515&w=2 :
> >
> > Georg Richter wrote:
> > > Unbelievable.
> > > Guess the postgres guys are licking their chops over this.
> > >
> > > > We need to use this opportunity to encourage PHP folks to switch to
> > > > PostgreSQL.
> > >
> > > Indeed. What can we do exactly?
> >
> > Probably the Postgres client library (that'd be libpq) can be included
> > as part of the PHP distribution. With that, according to the thread,
> > the Postgres support could be built in by default. I can't find the PHP
> > license on their website though.
>
> I don't quite understand this. I thought PostgreSQL library _is_ included with
> PHP distribution. All I needed to do to compile is put --with-pgsql in
> configuring php.
With PHP, when you type --with-pgsql it looks for the libs that postgresql
installed for connection. With the way MySQL support was installed, the
connection lib files were actually in the PHP source tree, and it by
default didn't use the ones installed by MySQL.
Note that this could actually cause issues if you compiled Apache with the
right setup to support mysql database authentication and it used the
installed mysql libs and php used its built in libs and they were
different versions you'd have a version of apache / PHP that would crash
randomly.
For this reason and many others, it is considered a bad design decision to
have included the connect libs in the PHP's source tree. It basically
made it easier for junior sys admins to shoot themselves in the foot.
:-)