| From: | darcy(at)druid(dot)net (D'Arcy J(dot)M(dot) Cain) |
|---|---|
| To: | Philip Warner <pjw(at)rhyme(dot)com(dot)au> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Michael J Schout <mschout(at)gkg(dot)net>, Alessio Bragadini <alessio(at)albourne(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Insert..returning (was Re: Re: postgres TODO) |
| Date: | 2000-07-12 09:14:16 |
| Message-ID: | m13CIav-000AXOC@druid.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Thus spake Philip Warner
> > Not to mention the juicy topics of access permissions and
> >possible errors.
>
> Can't one fall back here on the 'insert followed by select' analogy? Or is
> there a specific example that you have in mind?
I think the thing he has in mind is the situation where one has insert
perms but not select. The decision is whether to have the insert fail
if the select fails. Or, do you allow the (virtual) select in this
case since it is your own inserted row you are trying to read?
--
D'Arcy J.M. Cain <darcy(at){druid|vex}.net> | Democracy is three wolves
http://www.druid.net/darcy/ | and a sheep voting on
+1 416 425 1212 (DoD#0082) (eNTP) | what's for dinner.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zeugswetter Andreas SB | 2000-07-12 10:32:03 | AW: update on TOAST status' |
| Previous Message | Jan Wieck | 2000-07-12 09:05:21 | Re: Re: postgres TODO |