Re: [GENERAL] plPHP in core? - Mailing list pgsql-hackers

From Greg Stark
Subject Re: [GENERAL] plPHP in core?
Date
Msg-id 87k6njqil4.fsf@stark.xeocode.com
Whole thread Raw
In response to Re: [GENERAL] plPHP in core?  ("Jim C. Nasby" <decibel@decibel.org>)
List pgsql-hackers
"Jim C. Nasby" <decibel@decibel.org> writes:

> On Sun, Apr 03, 2005 at 08:41:15PM -0700, Joshua D. Drake wrote:
> >
> > > What databases support perl or php stored procs/functions? Or python for
> > > that matter?
> >
> > None on the server side (except PostgreSQL) which makes the
> > argument all that more powerful :)

Actually Oracle supports at least Perl and Java in addition to C for server
side code. And of course once you have C it's a SMOP to have PHP, Python, Ruby
or whatever so I wouldn't be surprised to find packages for any of those out
there.

> Honestly, I think if we're going to spend time worrying about languages
> as features then we should be doing more to advertise the fact that
> perl/PHP/python/ruby/etc programmers can program in the database in
> their native language. This is something that makes PostgreSQL unique
> and should provide additional incentive for people to use PostgreSQL. I
> don't think it matters much at all if those 'bonus languages' are
> included in core or not, at least not to end-users.

FWIW I agree. The extensibility of Postgres is its strong point. That you can
program the server easily and conveniently in your favourite language without
going through extra layers of abstraction or complicated build environments is
the biggest component of that.

-- 
greg



pgsql-hackers by date:

Previous
From: "Jim C. Nasby"
Date:
Subject: Re: [GENERAL] plPHP in core?
Next
From: Michael Glaesemann
Date:
Subject: BuildFarm status: recent check failures