Zeugswetter Andreas SB <[EMAIL PROTECTED]> writes:
>> select pg_class from pg_class;
> Probably a valid interpretation would be if type pg_class or opaque had an
> output function.
Hmm, good point. We shouldn't foreclose the possibility of handling
things that way. Okay, I'm convinced: allo
> True, although there's a certain inconsistency in allowing a whole row
> to be passed to a function by
>
> select foo(pg_class) from pg_class;
>
> and not allowing the same row to be output by
Imho there is a big difference between the two. The foo(pg_class) calls a function
with argu
> > I tend to agree that we should not change the code to make "select tab"
> > work, on the grounds of error-proneness.
>
> OK, here is another patch that does this:
>
> test=> select test from test;
>test
> --
> 1
> (1 row)
I object also. It is not a
