| From: | Philip Warner <pjw(at)rhyme(dot)com(dot)au> |
|---|---|
| To: | Michael J Schout <mschout(at)gkg(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Alessio Bragadini <alessio(at)albourne(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Insert..returning (was Re: Re: postgres TODO) |
| Date: | 2000-07-11 23:54:52 |
| Message-ID: | 3.0.5.32.20000712095452.01e34320@mail.rhyme.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
At 00:21 12/07/00 +1000, Philip Warner wrote:
>
>Well, not wanting to sound too much like a broken record,
>
> insert...returning...
>
>would seem to fix the problem.
>
>Is there some obvious (to anyone who knows something about pg internals)
>reason why this is *not* a good idea?
>
Putting this another way, does anyone object to this being implemented, *at
least* in the case of single row updates?
Secondly, can anyone suggest likely problems that would occur in a naieve
'do a select after an insert' or 'keep a list of affected oids' approach?
----------------------------------------------------------------
Philip Warner | __---_____
Albatross Consulting Pty. Ltd. |----/ - \
(A.C.N. 008 659 498) | /(@) ______---_
Tel: (+61) 0500 83 82 81 | _________ \
Fax: (+61) 0500 83 82 82 | ___________ |
Http://www.rhyme.com.au | / \|
| --________--
PGP key available upon request, | /
and from pgp5.ai.mit.edu:11371 |/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chris Bitmead | 2000-07-12 00:07:13 | Re: Slashdot discussion |
| Previous Message | Tim Perdue | 2000-07-11 23:51:08 | 7.0.2 issues / Geocrawler |