Insert..returning (was Re: Re: postgres TODO)

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   |/