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

From: Steve Atkins <steve(at)blighty(dot)com>
To: PostgreSQL General <pgsql-general(at)postgresql(dot)org>
Subject: Re: choiche of function language was: Re: dynamic procedure call
Date: 2008-05-10 14:27:01
Message-ID: 951B9F0D-B9BF-4B48-868C-BFB93CC6DAB3@blighty.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


On May 10, 2008, at 12:14 AM, Ivan Sergio Borgonovo wrote:

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

A much better impedance match to the database. It's designed for
doing database-ish things. The biggest advantage there is that
your datatypes are the database datatypes and your expression
parser is the sql expression parser. That makes using things like
timestamp or interval or custom database types simpler and cleaner
from pl/pgsql than from, say, pl/perl/

Cheers,
Steve

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2008-05-10 15:19:27 Re: choiche of function language was: Re: dynamic procedure call
Previous Message Josh Tolley 2008-05-10 11:25:37 Problem returning strings with pgsql 8.3.x