| From: | Philip Warner <pjw(at)rhyme(dot)com(dot)au> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Incomplete idea about views and INSERT...RETURNING |
| Date: | 2001-07-22 00:22:48 |
| Message-ID: | 3.0.5.32.20010722102248.02d566b0@mail.rhyme.com.au |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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 |/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tatsuo Ishii | 2001-07-22 00:28:03 | Re: SIGCHLD handler in Postgres C function. |
| Previous Message | Tom Lane | 2001-07-21 22:09:28 | Re: WIN32 errno patch |