Re: Specific names for plpgsql variable-resolution control options? - Mailing list pgsql-hackers

From David E. Wheeler
Subject Re: Specific names for plpgsql variable-resolution control options?
Date
Msg-id C889611E-AE8F-4D0C-8F1F-9FF47A84A056@kineticode.com
Whole thread Raw
In response to Re: Specific names for plpgsql variable-resolution control options?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Specific names for plpgsql variable-resolution control options?
List pgsql-hackers
On Nov 6, 2009, at 4:57 PM, Tom Lane wrote:

>> plpgsql_variable_conflict = fatal | oracle-compat | pg-compat
>
> plpgsql_variable_conflict is all right, but I think we should avoid
> using Oracle's trademarked name in the setting names.  I was  
> envisioning
> setting names related to "variable first" or "column first" or  
> something
> in that line.

That works.
  plpgsql_variable_conflict = fatal | variable-first | column-first

David


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: operator exclusion constraints
Next
From: Andrew Dunstan
Date:
Subject: Re: plperl and inline functions -- first draft