From: | Bernd Helmle <mailings(at)oopsware(dot)de> |
---|---|
To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: mixed, named notation support |
Date: | 2009-07-23 18:48:26 |
Message-ID: | DADFACCFF537E9A8F7CA2F3C@teje |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
--On Donnerstag, März 05, 2009 08:41:28 +0100 Pavel Stehule
<pavel(dot)stehule(at)gmail(dot)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?
--
Thanks
Bernd
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2009-07-23 19:08:29 | Re: mixed, named notation support |
Previous Message | Jaime Casanova | 2009-07-23 18:45:00 | Re: Determining client_encoding from client locale |