Re: mixed, named notation support - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: mixed, named notation support
Date
Msg-id 162867790907252117n30f09c4el71df1d7fddcaef93@mail.gmail.com
Whole thread Raw
In response to Re: mixed, named notation support  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: mixed, named notation support
List pgsql-hackers
Hi,

I sending a little bit modified version - I removed my forgotten
comment in gram.y

Regards
Pavel

2009/7/25 Pavel Stehule <pavel.stehule@gmail.com>:
> Hello,
>
> fixed patch attached + more regress tests.
>
> Regards
> Pavel Stehule
>
>
> 2009/7/23 Pavel Stehule <pavel.stehule@gmail.com>:
>> 2009/7/23 Bernd Helmle <mailings@oopsware.de>:
>>> --On Donnerstag, März 05, 2009 08:41:28 +0100 Pavel Stehule
>>> <pavel.stehule@gmail.com> wrote:
>>>
>>>> Hello
>>>>
>>>> I did some cleaning on this feature, and I hope so I solve some Tom's
>>>> objections
>>>>
>>>> features:
>>>>  * PostgreSQL's specific syntax for named parameter: value AS name,
>>>>  * Doesn't change rules for defaults,
>>>>  * Get defaults for named, mixed notation in planner time.
>>>>
>>>
>>> Pavel, consider the following function:
>>>
>>> CREATE OR REPLACE FUNCTION ftest(a int, b text)
>>> RETURNS RECORD
>>> LANGUAGE SQL
>>> AS
>>> $$
>>>       SELECT $1, $2 ;
>>> $$;
>>>
>>> #= SELECT ftest('blubb' AS b, 128 AS a);
>>> ERROR:  function ftest(unknown, integer) does not exist at character 8
>>>
>>> #= SELECT ftest(128 AS a, 'abcd' AS b);
>>>  ftest
>>> ------------
>>> (128,abcd)
>>> (1 row)
>>>
>>> Isn't the first one supposed to work?
>>
>> it is probably bug. I'll look on it tomorrow.
>>
>> Pavel
>>
>>>
>>>
>>> --
>>>  Thanks
>>>
>>>                   Bernd
>>>
>>
>

Attachment

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Patch for 8.5, transformationHook
Next
From: KaiGai Kohei
Date:
Subject: Re: SE-PostgreSQL Specifications