Re: [GENERAL] plPHP in core?

From: Greg Stark <gsstark(at)mit(dot)edu>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [GENERAL] plPHP in core?
Date: 2005-04-05 03:37:43
Message-ID: 874qelq4fs.fsf@stark.xeocode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl> writes:

> Because those other languages are well designed and PHP is not. The
> Postgres support package for Perl is a completely separate add-on, which
> you can add well after the core of Perl is installed. Same for Python.
> But PHP is a braindead package which includes the Postgres support in
> the main codebase.

Oh egads. I finally understand this whole thread. You guys are all talking
about the old-fashioned Postgres support that has special pg* functions that
deal only with Postgres.

There are PHP modules that abstract that all away now, much like DBD::Pg, and
I believe they can be build as external modules. So I'm not sure how much this
matters any more. Perhaps it's still a factor for another release or two
though.

I'm surprised Tom's concerned about this. It's especially not relevant for
distribution based systems like Debian or Redhat. There are tons of circular
build dependencies in a complete distribution (think of the compiler toolchain
for example) and packagers can just download binary packages for the packages
they aren't developing at the time.

--
greg

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Michael Fuhr 2005-04-05 03:45:45 Re: How to dump data from database?
Previous Message Greg Sabino Mullane 2005-04-05 02:46:18 Re: [GENERAL] plPHP in core?

Browse pgsql-hackers by date

  From Date Subject
Next Message Christopher Kings-Lynne 2005-04-05 03:46:22 PgFoundry.org busted?
Previous Message Greg Stark 2005-04-05 03:32:47 Re: Notes on lock table spilling