Re: mixed, named notation support

From: Bernd Helmle <mailings(at)oopsware(dot)de>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Steve Prentice <prentice(at)cisco(dot)com>, PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: mixed, named notation support
Date: 2009-08-09 17:52:35
Message-ID: 5E1FFA0BBC363F284009F266@amenophis
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

--On 9. August 2009 13:00:07 -0400 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Mph. Does Oracle adopt the same semantics for what a mixed call means?

I had a look at the Oracle documentation while reviewing this patch, and i
thought we are pretty close to what they do. Maybe Pavel can comment more
on it.

> Because my next complaint was going to be that this definition was
> poorly chosen anyway --- it seems confusing, unintuitive, and
> restrictive. If the function is defined as having parameters (a,b,c)
> then what does this do:
>
> select foo(1, 2, 3 as b);
>
> and what's the argument for having it do that rather than something
> else?

Since b is ambiguous we error out (I don't know what Oracle does, but i
would be surprised if they do anything different).

--
Thanks

Bernd

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2009-08-09 17:53:20 Re: mixed, named notation support
Previous Message Boszormenyi Zoltan 2009-08-09 17:24:37 Re: Split-up ECPG patches