Обсуждение: Re: BUG #7644: Missing implicit types of Result and failing type-conversion

"Bernhard Reutner-Fischer" <rep.dot.nop@gmail.com> writes:
> Fair enough but what about the failure for the case with the Result
> that fails to merge? There I do have a cast

No you don't:

>         select * from (select 'string two' bug ) s2

            regards, tom lane

On 10 November 2012 16:58, Tom Lane <tgl@sss.pgh.pa.us> wrote:

> "Bernhard Reutner-Fischer" <rep.dot.nop@gmail.com> writes:
> > Fair enough but what about the failure for the case with the Result
> > that fails to merge? There I do have a cast
>
> No you don't:
>
> >         select * from (select 'string two' bug ) s2
>
>                         regards, tom lane
>

I do not need the cast in the second select when using generate_series
either.

select distinct on (bug) bug
from (
   select * from (select 'string one'::text bug from generate_series(0,1))
s1
   UNION
   select * from (select 'string two' bug) s2
-- select * from (select 'string two' bug from generate_series(0,0)) s2
) x
;

IMO this contradicts the "Type Resolution for UNION, CASE, and Related
Constructs" from the documentation.
4) Choose the first non-unknown input type which is a preferred type in
that category, if there is one.

Please explain why the two selects for 'string two' in the example above
behave different?

Many TIA && cheers,