Re: php as stored procedures

PHP is nice, but it's designed for a very specific purpose -- to write web
based applications quickly. Having it in a DB is a little silly if you ask
me.. Pl/pgsql is nice for smaller functions, C is great for everything else
and of course, if you're a Perl monk, use it! :-)

Pl/PHP is possible (simply because anything is possible) but I doubt you'll
see any of the core developers doing anything of the sort though.. However,
I'm sure they'd encourage anyone to write anything they wanted so go for it!

Pl/Ruby - there is an idea *grin*

-Mitch

----- Original Message -----
From: "Adam Lang" <aalang(at)rutgersinsurance(dot)com>
To: <pgsql-general(at)postgresql(dot)org>
Sent: Wednesday, January 31, 2001 1:43 PM
Subject: Re: php as stored procedures

> I remember a year ago when I was looking at open source DBs, MySQL was
> supposed to be getting php script support inside the database.
>
> As for having a pl/PHP, I do not believe it is a dire need. If it would
> make someone's life easier, fine, I don't see why it couldn't be coded and
> added... I just don't see it as something the steering committee
> should/would use their time on. It should be a project that is done on
the
> outside and submitted in.
>
> The way I see it (as for adding languages to postgres) is a lot like what
> Microsoft does for their scripting language. You set up basic core
> functionality that supports the most users (WSH, VBScript, and Jscript)
and
> then have it so that other developers can make add-ons to support other
> languages. As an example, you can get a python and/or perl engine that
will
> run over the Windows Scripting Host. Perl script on Windows isn't
something
> overly important for MS to support, but the functionality was there to
allow
> someone that did see a need for it to be able to develop add-ons for it.
> I'd say something along the lines of pl/ languages work the same way. The
> major ones are supported, if someone wants to add more, more power to
them.
>
> Adam Lang
> Systems Engineer
> Rutgers Casualty Insurance Company
> http://www.rutgersinsurance.com
> ----- Original Message -----
> From: "Doug McNaught" <doug(at)wireboard(dot)com>
> To: <pgsql-general(at)postgresql(dot)org>
> Sent: Wednesday, January 31, 2001 12:15 PM
> Subject: Re: [GENERAL] php as stored procedures
>
>
> > mwaples(at)waples(dot)net writes:
> >
> > > I was reading
> > > http://www.linuxworld.com.au/article.php3?aid=123&tid=8
> > > and specifically
> > > "Later in 2001 this flexibility may extend even within the MySQL
> > > database server, with PHP scripts used as stored procedures within
MySQL
> > > database"
> > > I won't hold my breath for that to happen in 2001 knowing MYsql's many
> > > promised future features but it got me wondering
> > >
> > > Since there is pl/perl is it all remotely possible that a pl/php could
> > > be implemented ?
> >
> > Well, in software, you can do pretty much anything with enough
> > hacking, so it's definitely possible.
> >
> > As for whether it will be done, well, what does PHP give you over
> > Perl? I know Perl well and PHP AFAICS is a tiny subset of Perl
> > designed to be embedded in web pages. Given PL/Perl, do we really
> > need PL/PHP?
> >
> > If someone (you?) think's it's important it'll probably get written.
> >
> > -Doug
>
>