Re: PATCH: make plpgsql IN args mutable (v1) [REVIEW]

From: Abhijit Menon-Sen <ams(at)toroid(dot)org>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org, Steve Prentice <prentice(at)cisco(dot)com>
Subject: Re: PATCH: make plpgsql IN args mutable (v1) [REVIEW]
Date: 2009-09-16 12:46:59
Message-ID: 20090916124659.GA1797@toroid.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

At 2009-09-16 08:37:40 -0400, andrew(at)dunslane(dot)net wrote:
>
> How does this compare with PLSQL?

I don't remember anything of PL/SQL myself, but Pavel Stehule had this
to say in response to the original post:

> This behave is in conflict with PL/SQL, what should do some problems.
> I thing, so I understand well, why this behave is in PL/SQL. It hasn't
> sense in plpgsql, because OUT and INOUT params has little bit
> different syntax (calling) and nobody will do similar bugs (perhaps).
> What is interesting - this behave is in conformity with SQL/PSM, where
> parameters are mutable too.
>
> I am for it. PL/pgSQL doesn't promise compatibility with PL/SQL and
> this change should to help some beginners (and this limit is
> artificial and unnecessary).

Given the existing OUT/INOUT syntax difference as noted, I don't think
the patch represents a significant problem.

-- ams

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2009-09-16 12:59:36 Re: PATCH: make plpgsql IN args mutable (v1) [REVIEW]
Previous Message Alvaro Herrera 2009-09-16 12:46:43 Re: pg_hba.conf: samehost and samenet