Re: Re: postgres TODO - Mailing list pgsql-hackers

From Philip Warner
Subject Re: Re: postgres TODO
Date
Msg-id 3.0.5.32.20000712002122.02705c20@mail.rhyme.com.au
Whole thread Raw
In response to Re: Re: postgres TODO  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Insert..returning (was Re: Re: postgres TODO)
List pgsql-hackers
At 09:07 11/07/00 -0500, Michael J Schout wrote:
>
>Anyways, its easy enough to get at the information this way without making
your
>application depend on OID values.  Yes, you might still get bunt by triggers.
>I am not sure if there is an easy solution to that.
>

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?


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


pgsql-hackers by date:

Previous
From: Zeugswetter Andreas SB
Date:
Subject: AW: postgres 7.2 features.
Next
From: Bruce Momjian
Date:
Subject: Re: Re: C language function dump problem