Re: [PERFORM] typoed column name, but postgres didn't grump - Mailing list pgsql-bugs

From Kevin Grittner
Subject Re: [PERFORM] typoed column name, but postgres didn't grump
Date
Msg-id 4CD28C5C020000250003727B@gw.wicourts.gov
Whole thread Raw
In response to Re: [PERFORM] typoed column name, but postgres didn't grump  (Merlin Moncure <mmoncure@gmail.com>)
Responses Re: [PERFORM] typoed column name, but postgres didn't grump
List pgsql-bugs
Merlin Moncure <mmoncure@gmail.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

pgsql-bugs by date:

Previous
From: Merlin Moncure
Date:
Subject: Re: [PERFORM] typoed column name, but postgres didn't grump
Next
From: Tom Lane
Date:
Subject: Re: [PERFORM] typoed column name, but postgres didn't grump