| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Dave Cramer <pg(at)fastcrypt(dot)com> |
| Cc: | Martijn van Oosterhout <kleptog(at)svana(dot)org>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Neil Conway <neilc(at)samurai(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: PostgreSQL roadmap for 8.2 and beyond. |
| Date: | 2005-10-17 18:37:42 |
| Message-ID: | 10584.1129574262@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Dave Cramer <pg(at)fastcrypt(dot)com> writes:
> On 17-Oct-05, at 1:43 PM, Martijn van Oosterhout wrote:
>> ISTM them that the RETURNING patch as given solves your problem
>> nicely.
> Well, the driver still needs to know ahead of time which columns are
> going to be autogenerated.
Possibly you could define that as "all columns that are not specified in
the INSERT command and have column default expressions". The first is
knowable with very little parsing of the command, and the second can be
learned from the catalog metadata that you're probably reading anyway.
If the JDBC spec has a more specific definition of "autogenerated" than
"has a default", then what is it?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-10-17 18:41:00 | Re: PostgreSQL roadmap for 8.2 and beyond. |
| Previous Message | Martijn van Oosterhout | 2005-10-17 18:09:47 | Re: libpq's pollution of application namespace |