From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
---|---|
To: | "Merlin Moncure" <mmoncure(at)gmail(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Robert Haas" <robertmhaas(at)gmail(dot)com>, "Jon Nelson" <jnelson+pgsql(at)jamponi(dot)net>, <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: [PERFORM] typoed column name, but postgres didn't grump |
Date: | 2010-11-04 15:35:08 |
Message-ID: | 4CD28C5C020000250003727B@gw.wicourts.gov |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-performance |
Merlin Moncure <mmoncure(at)gmail(dot)com> wrote:
> Trying to understand real world cases that this would
> break...would the following now fail w/o explicit cast?
>
> create type x as (a int, b int);
> select f((1,2));
It already does:
test=# create type x as (a int, b int);
CREATE TYPE
test=# select f((1,2));
ERROR: function f(record) does not exist
LINE 1: select f((1,2));
^
HINT: No function matches the given name and argument types. You
might need to add explicit type casts.
-Kevin
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-11-04 16:14:45 | Re: [PERFORM] typoed column name, but postgres didn't grump |
Previous Message | Merlin Moncure | 2010-11-04 15:24:05 | Re: [PERFORM] typoed column name, but postgres didn't grump |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-11-04 16:14:45 | Re: [PERFORM] typoed column name, but postgres didn't grump |
Previous Message | Merlin Moncure | 2010-11-04 15:24:05 | Re: [PERFORM] typoed column name, but postgres didn't grump |