At 18:03 21/07/01 -0400, Tom Lane wrote: > >Could we get away with restricting INSERT RETURNING to work only on >inserts directly to tables (no ON INSERT DO INSTEAD allowed)? Or is >that too much of a kluge? > I don't see it as a kludge, just a limitation on the first pass. If people need the feature then they can recode their DO INSTEAD as a trigger (I think that works...). You probably need to return useful information to the application to let it know what has happened, however. ---------------------------------------------------------------- Philip Warner | __---_____ Albatross Consulting Pty. Ltd. |----/ - \ (A.B.N. 75 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 |/ ---------------------------(end of broadcast)--------------------------- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
