Re: Some notes about Param handling with "Oracle style" plpgsql variables - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: Some notes about Param handling with "Oracle style" plpgsql variables
Date
Msg-id 162867790911021118j143736f5rb84100fd18205bb3@mail.gmail.com
Whole thread Raw
In response to Re: Some notes about Param handling with "Oracle style" plpgsql variables  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
2009/11/2 Tom Lane <tgl@sss.pgh.pa.us>:
> Pavel Stehule <pavel.stehule@gmail.com> writes:
>> 2009/11/2 Tom Lane <tgl@sss.pgh.pa.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.

good

regards
Pavel
>
>                        regards, tom lane
>


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Some notes about Param handling with "Oracle style" plpgsql variables
Next
From: Tom Lane
Date:
Subject: Re: Renaming conversion procs (was Re: [GENERAL] Error on compile for Windows)