| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Chris Bitmead <chrisb(at)nimrod(dot)itg(dot)telstra(dot)com(dot)au> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Chris <chris(at)bitmead(dot)com>, Postgres Hackers List <hackers(at)postgresql(dot)org> |
| Subject: | Re: OO Patch |
| Date: | 2000-05-19 05:09:51 |
| Message-ID: | 6530.958712991@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
Chris Bitmead <chrisb(at)nimrod(dot)itg(dot)telstra(dot)com(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chris Bitmead | 2000-05-19 05:29:12 | Re: OO Patch |
| Previous Message | Chris Bitmead | 2000-05-19 04:38:44 | Re: OO Patch |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chris Bitmead | 2000-05-19 05:29:12 | Re: OO Patch |
| Previous Message | Chris Bitmead | 2000-05-19 05:01:59 | OO / fe-be protocol |