| From: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
|---|---|
| To: | Ewald Geschwinde <egeschwinde(at)gmail(dot)com> |
| Cc: | 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 08:59:05 |
| Message-ID: | 20070611085905.GA25296@svana.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Jun 11, 2007 at 09:40:08AM +0200, Ewald Geschwinde wrote:
> My problem is that some users don't have access to change the structure but
> they wanted to delete all data from the table
> they try truncate - does not work because not the owner
> so they make a delete from a really big table
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?
Have a nice day,
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2007-06-11 09:04:41 | Re: Truncate Permission |
| Previous Message | Pavel Stehule | 2007-06-11 08:33:16 | ToDO, support UPDATE/DELETE WHERE CURRENT OF cursor_name in plpgsql |