Re: Some notes about Param handling with "Oracle style" plpgsql variables

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Some notes about Param handling with "Oracle style" plpgsql variables
Date: 2009-11-02 19:16:15
Message-ID: 7391.1257189375@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> writes:
> 2009/11/2 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
>> This kinda calls into question whether the Oracle way is actually
>> a good idea or not; but my purpose here is not to debate that,
>> just to look at what it takes to implement it.

> This is reason, why I would to see third mode (incompatible with
> Oracle or pg), that raise error, when it detects any intersecting
> identifiers. I understand so this mode should not be default, but
> personally I'll use it everywhere.

Actually, I thought we'd decided that "throw error on conflict"
*would* be the default behavior.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2009-11-02 19:18:14 Re: Some notes about Param handling with "Oracle style" plpgsql variables
Previous Message Pavel Stehule 2009-11-02 19:05:23 Re: Some notes about Param handling with "Oracle style" plpgsql variables