| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Hannu Krosing <hannu(at)tm(dot)ee> |
| Cc: | Chris Bitmead <chrisb(at)nimrod(dot)itg(dot)telstra(dot)com(dot)au>, 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 21:20:01 |
| Message-ID: | 9808.958771201@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
Hannu Krosing <hannu(at)tm(dot)ee> writes:
>> Certainly libpq is unprepared to support
>> multiple tuple types returned in one SELECT
> IIRC Bruce removed that feature in Pg95 days claiming that it would
> not be needed. If backend starts to support it again it would be
> relatively easy to put back in.
Would it? libpq's internals might not care much, but it seems to me
that a rather significant API change would be needed, thus risking
breaking client applications. I'd want to see how the libpq API
changes before deciding how easy or hard this is ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hiroshi Inoue | 2000-05-19 22:01:15 | RE: Performance (was: The New Slashdot Setup (includes MySql server)) |
| Previous Message | Tom Lane | 2000-05-19 21:16:41 | Re: OO Patch |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hiroshi Inoue | 2000-05-19 22:01:15 | RE: Performance (was: The New Slashdot Setup (includes MySql server)) |
| Previous Message | Tom Lane | 2000-05-19 21:16:41 | Re: OO Patch |