Re: plPHP -- sort of an announcement.. but not commercial

From: "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl>, <pgsql-general(at)postgresql(dot)org>
Subject: Re: plPHP -- sort of an announcement.. but not commercial
Date: 2003-08-05 17:00:49
Message-ID: Pine.LNX.4.33.0308051100050.13527-100000@css120.ihs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Tue, 5 Aug 2003, Peter Eisentraut wrote:

> Tom Lane writes:
>
> > (Including PLs in the standard distro strikes me as a good idea, BTW.
> > They usually need maintenance along with the core backend code.)
>
> We could also say that keeping some PLs outside the core would keep us
> more honest in keeping the interfaces stable. The only maintenance that
> PLs really need to get are global search-and-replace bug fixes and making
> use of new server features.
>
> Consider, we already have (at least) Ruby, Sh, R, and Java language
> handlers out there, and we're not putting all of these in the core anytime
> soon. The handlers we currently have in the core cover the most popular
> languages, but there should be room for serious external development.
>
> Btw., one concern I have about putting this PHP thing in the core is that
> it would create a circular build dependency between PostgreSQL and PHP.

Agreed. I still want to know if we can have "safe mode" enabled and make
a trusted / untrusted version. Is that workable? I would very much like
to have a trusted version.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Richard Welty 2003-08-05 17:35:58 indices and cidr/inet type
Previous Message Christopher Murtagh 2003-08-05 16:58:33 Re: Changing DB ownership