Re: WIP: default values for function parameters - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: WIP: default values for function parameters
Date
Msg-id 162867790812100914t23cfd533g79e95a40f6c8f876@mail.gmail.com
Whole thread Raw
In response to Re: WIP: default values for function parameters  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
2008/12/10 Tom Lane <tgl@sss.pgh.pa.us>:
> "Pavel Stehule" <pavel.stehule@gmail.com> writes:
>> 2008/12/10 Bruce Momjian <bruce@momjian.us>:
>>> Well, that is interesting, but in SQL we already use 'AS' in most places
>>> where we want to assign a label to a value, so it seems AS is more
>>> logical for SQL at this point.
>
>> Question is - what is label - is it parameter name or some other value?
>
>> Every output in SQL has default label - column name, or some default.
>> And we use "AS" for change this default label. So using AS for param
>> names is bad idea.
>
> That argument is complete nonsense.  A function parameter can't possibly
> be an "output" of a SQL statement, so there is no conflict.
>

we speaking about two things probably. I speaking so using AS in two
independent meaning is wrong.

look again
select c as foo from tab ...
select fce(c as foo) from tab ...

when you use AS as param names specification, you change meaning of
some construct via used context?

is it true or false?

regards
Pavel Stehule


>                        regards, tom lane
>


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: WIP: default values for function parameters
Next
From: Zdenek Kotala
Date:
Subject: Re: cvs head initdb hangs on unixware