Re: Specific names for plpgsql variable-resolution control options?

From: "David E(dot) Wheeler" <david(at)kineticode(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: Specific names for plpgsql variable-resolution control options?
Date: 2009-11-07 02:45:14
Message-ID: C889611E-AE8F-4D0C-8F1F-9FF47A84A056@kineticode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2009-11-07 02:53:20 Re: plperl and inline functions -- first draft
Previous Message Andrew Dunstan 2009-11-07 02:44:15 Re: operator exclusion constraints