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
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.
In response to
pgsql-hackers by date
|Next:||From: Christopher Kings-Lynne||Date: 2005-04-05 03:46:22|
|Subject: PgFoundry.org busted?|
|Previous:||From: Greg Stark||Date: 2005-04-05 03:32:47|
|Subject: Re: Notes on lock table spilling|
pgsql-general by date
|Next:||From: Michael Fuhr||Date: 2005-04-05 03:45:45|
|Subject: Re: How to dump data from database?|
|Previous:||From: Greg Sabino Mullane||Date: 2005-04-05 02:46:18|
|Subject: Re: [GENERAL] plPHP in core?|