Hi,

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.

Offered by command prompt:
http://www.commandprompt.com/community/plphp/

Did anybody in here use it?
What are your experiences?
Any advise?

Regards,
Erwin Moller

Erwin Moller wrote:

Hi,
>
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.
>
Offered by command prompt:
http://www.commandprompt.com/community/plphp/
>
Did anybody in here use it?
What are your experiences?
Any advise?
>
Regards,
Erwin Moller

Ullo Erwin.

Not with Postgres, but its cool with MySql.

What ever rocks yer boat...if it works for you,use it.

PHP has its irritations, but I find it infinitely preferable to other
languages like *shudder* PERL..

The Natural Philosopher wrote:

Erwin Moller wrote:
>

>
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.

--
Toby A Inkster BSc (Hons) ARCS
[Geek of HTML/SQL/Perl/PHP/Python/Apache/Linux]
[OS: Linux 2.6.17.14-mm-desktop-9mdvsmp, up 3:50.]

Best... News... Story... Ever!
http://tobyinkster.co.uk/blog/2008/03/23/hypnotist/

Toby A Inkster wrote:

The Natural Philosopher wrote:

>
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.
>

Muy Bad.

Toby A Inkster schreef:

The Natural Philosopher wrote:

>
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