Chris Bitmead <chrisb@nimrod.itg.telstra.com.au> writes:
> 3) Returning of sub-class fields. Any ODBMS *must* do this by
> definition. If it doesn't, it isn't an ODBMS.
Chris, you have a bad habit of defining away the problem. Not
everyone is convinced upon this point, and your assertions that
there was consensus don't help your cause.
Possibly more to the point: your patch doesn't implement the
above behavior AFAICS. (Certainly libpq is unprepared to support
multiple tuple types returned in one SELECT --- and there are no
frontend changes in your patch.) So it might help if you'd clarify
exactly what the proposed patch does and doesn't do.
regards, tom lane