Toby A Inkster schreef:
Quote:
The Natural Philosopher wrote:
Quote:
>Erwin Moller wrote:
>>
Quote:
>>I was surprised to see that my fav. database offers PHP as a scripting
>>language Procedural language (eg stored procedures). Untill now I
>>always used PgPL/SQL for that.
>Not with Postgres, but its cool with MySql.
>
I think you misunderstand Erwin's post. He's talking about the programming
language used for creating stored procedures within the database. That is,
not accessing database from a script, but the other way around: accessing
a script from the database.
>
See <http://en.wikipedia.org/wiki/Stored_procedure>.
>
MySQL only supports stored procedures written in SQL. (And has only
supported stored procedures *at all* since 5.0.)
>
PostgreSQL allows you to use SQL, C, Tcl, Perl or Python and allows you to
use others through plugins. Plugins are available for Java, Shell script,
and Scheme amongst others.
>
Erwin posted a link to a plugin allowing the use of PHP as a scripting
language within PostgreSQL. Indeed it looks doubleplusgood. I tend to use
PgPL/SQL (and T-SQL on MS SQL server) but will certainly give this a try.
>
Yes, indeed.
I wasn't talking about accessing Postgresql through PHP, which has been
my hobby for years anyway. ;-)
100% personal perspective:
I have never been very confortable with PgPL/SQL 'scripting language'
inside procedures, and tend to solve as much as possible inside the main
PHP script.
I have had a few nasty bugs, totally created by myself, by using stored
procedures that seemed an easy way out of a nasty problem, at that time...
Using procedures just adds another layer of possible problems, and I
find them harder to spot than pure PHP bugs.
That is why I avoid using SPs, if possible, partly because I don't like
the PgPL/SQL language too much.
But now we can use PHP for that... yummy. :-)
I'll just give it a shot, and see how it works.
Regards,
Erwin Moller
