| From: | Stephen Frost <sfrost(at)snowman(dot)net> |
|---|---|
| To: | Zeugswetter Andreas ADI SD <ZeugswetterA(at)spardat(dot)at> |
| Cc: | Heikki Linnakangas <heikki(at)enterprisedb(dot)com>, Martijn van Oosterhout <kleptog(at)svana(dot)org>, Ewald Geschwinde <egeschwinde(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Nick Barr <nicky(at)chuckie(dot)co(dot)uk>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Truncate Permission |
| Date: | 2007-06-11 11:49:20 |
| Message-ID: | 20070611114920.GQ7531@tamriel.snowman.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
* Zeugswetter Andreas ADI SD (ZeugswetterA(at)spardat(dot)at) wrote:
>
> > > Wouldn't it be far more logical to decide that if a user has the
> > > permissions to do a DELETE FROM table; then they have permission to
> do
> > > a TRUNCATE? Why make an additional permission?
> >
> > Truncate doesn't fire ON DELETE triggers.
>
> Yes, but it would imho be ok if there are'nt any on delete triggers on
> the table.
Nope, it doesn't follow MVCC rules properly either. It really needs to
be a seperate permission.
Thanks,
Stephen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Meskes | 2007-06-11 12:02:23 | Re: ecpg leaves broken files around |
| Previous Message | Timasmith | 2007-06-11 11:38:55 | one click install? |