Re: named parameters in SQL functions

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: named parameters in SQL functions
Date: 2009-11-16 01:22:20
Message-ID: 4B00A94C.2090105@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>
>> At Tom's suggestion I am looking at allowing use of parameter names in
>> SQL functions instead of requiring use of $1 etc. That raises the
>> question of how we would disambiguate a parameter name from a column
>> name.
>>
>
> Throw error if ambiguous. We already resolved this in the context of
> plpgsql.
>
>
>

Well, if the funcname.varname gadget will work, as you suggest elsewhere
it could, I think that would suffice. I had assumed that was just
something in the plpgsql engine.

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2009-11-16 01:32:35 Re: Patch committers
Previous Message Andrew Dunstan 2009-11-16 01:14:36 Re: patch - Report the schema along table name in a referential failure error message