| From: | Chris Bitmead <chrisb(at)nimrod(dot)itg(dot)telstra(dot)com(dot)au> |
|---|---|
| To: | "pgsql-hackers(at)postgreSQL(dot)org" <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | OO enhancements |
| Date: | 2000-07-13 07:17:12 |
| Message-ID: | 396D6CF8.3EFEA85A@nimrod.itg.telecom.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom, and others...
I've made modifications to libpq to accept multiple return type groups,
and now the thing to do is to make the back-end generate them from OO
hierarchies. Do you have any thoughts on the general approach to do
this? Should I be doing something like expandAll in parse_relation.c to
cater for different types? Do I play with ExecProject? Can anybody
remember anything about how postgres originally handled differing return
types?
Chris.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephan Szabo | 2000-07-13 07:31:38 | Questions relating to "modified while in use" messages |
| Previous Message | Tom Lane | 2000-07-13 07:13:19 | Re: Re: postgres TODO |