Re: choiche of function language was: Re: dynamic procedure call

From: "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com>
To: "Ivan Sergio Borgonovo" <mail(at)webthatworks(dot)it>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: choiche of function language was: Re: dynamic procedure call
Date: 2008-05-10 10:08:42
Message-ID: 162867790805100308y678dc477h2dcdc079d98b58bb@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hello

2008/5/10 Ivan Sergio Borgonovo <mail(at)webthatworks(dot)it>:
> On Sat, 10 May 2008 07:35:36 +0200
> "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com> 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?
>

SQL integration and compatibility with PostgreSQL. PL/pgSQL uses
PostgreSQL expression evaluation - so all PostgreSQL functions are
simply accessible from plpgsql. Next - plpgsql variables are
compatible (are same) with PostgreSQL internal datatypes - so you
don't need any conversion between Postgres and plpgsql.

plpgsql is best glue of SQL statements.

Pavel

> --
> Ivan Sergio Borgonovo
> http://www.webthatworks.it
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Pavel Stehule 2008-05-10 10:13:46 Re: Returning RECORD from PGSQL without custom type?
Previous Message Gerald Quimpo 2008-05-10 08:54:10 Re: Extract only numbers from a varchar column