Re: BUG #5974: UNION construct type cast gives poor error message - Mailing list pgsql-bugs

From Kevin Grittner
Subject Re: BUG #5974: UNION construct type cast gives poor error message
Date
Msg-id 4DA5CADB020000250003C7BE@gw.wicourts.gov
Whole thread Raw
In response to Re: BUG #5974: UNION construct type cast gives poor error message  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: BUG #5974: UNION construct type cast gives poor error message
List pgsql-bugs
Tom Lane <tgl@sss.pgh.pa.us> wrote:

> Consider
>
>     select '1' union select '1 ';
>
> How many rows does that produce?  You cannot answer without
> imputing a data type to the columns.  "text" will give a different
> answer than "integer" or "bpchar".

Well, if we were to assign both to type unknown initially, we would
clearly need to resolve that before execution,  But I'm not
expecting that such execution would happen before analyzing the rest
of the query.  If the above is on the left side of a union with

    select 1;

the unknown could then be resolved to integer.  I expect that all of
this should happen before any of the unions is *executed*.  Perhaps
I'm arguing for the same thing you were, but just have my head
tilted at a different angle?

-Kevin

pgsql-bugs by date:

Previous
From: "Paul Deschamps"
Date:
Subject: BUG #5978: Running postgress in a shell script fails
Next
From: Tom Lane
Date:
Subject: Re: BUG #5974: UNION construct type cast gives poor error message