[EMAIL PROTECTED] (Ivan Sergio Borgonovo) writes: > On Sat, 10 May 2008 07:35:36 +0200 > "Pavel Stehule" <[EMAIL PROTECTED]> wrote: > >> your application different execution paths. Generally I can say, so >> plpgsql isn't well language for this games, and better is using >> plperl, plpython or other external language. > > It is clear what is at least one of the advantage of plpython or > plperl over plpgsql, but then what are the advantages of plpgsql over > the rest of the crowd other than resembling the language used in > Oracle?
Well, plpgsql has the merit that its operations and control structures are directly oriented towards "database stuff," so there's no need to (for instance) invoke functions (e.g. - running queries via spi_exec(), spi_query(), ...) in order to perform database operations. One of the salutory effects is that there is a pl/pgsql debugger that can automatically handle things like single-stepping, and it does not need to be aware of any Perl/Python internals. -- "cbbrowne","@","linuxfinances.info" http://linuxfinances.info/info/sap.html "...you might as well skip the Xmas celebration completely, and instead sit in front of your linux computer playing with the all-new-and-improved linux kernel version." -- Linus Torvalds -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
