Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: Better error message for select_common_type()
- From: Peter Eisentraut <peter_e(at)gmx(dot)net>
- To: Gregory Stark <stark(at)enterprisedb(dot)com>
- Cc: pgsql-hackers(at)postgresql(dot)org
- Subject: Re: Better error message for select_common_type()
- Date: Tue, 24 Apr 2007 00:11:29 +0200
- Message-id: <200704240011(dot)30528(dot)peter_e(at)gmx(dot)net>
Gregory Stark wrote:
> "Peter Eisentraut" <peter_e(at)gmx(dot)net> writes:
> > peter=# values(0,1), (1::bigint,2), ('text'::text,3);
> > ERROR: 42804: VALUES types bigint at position 2 and text at
> > position 3 cannot be matched in instance 1
> >
> > I'm not sure about the terminology "position" and "instance";
> > they're just two coordinates to get at the problem.
>
> Wouldn't that just be column 1 in rows 2 and 3?
In this case yes, but the routine is also used for UNION, IN, GREATEST,
JOIN/USING and others.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
- References:
- Better error message for select_common_type()
- From: Peter Eisentraut
- Re: Better error message for select_common_type()
- From: Gregory Stark
- Better error message for select_common_type()
- Prev by Date: Re: RETURN QUERY in PL/PgSQL?
- Next by Date: Re: Wild idea: 9.0?
- Previous by thread: Re: Better error message for select_common_type()
- Next by thread: Re: Better error message for select_common_type()
- Indexes: