| From: | Leif Jensen <leif(at)crysberg(dot)dk> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>, Charles Clavadetscher <clavadetscher(at)swisspug(dot)org>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Delete trigger |
| Date: | 2015-09-18 13:06:14 |
| Message-ID: | 2102028613.5272565.1442581574404.JavaMail.zimbra@crysberg.dk |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi Ioana and David.
Thank you. Yes, I can see the problem. I will look into your suggestions.
Leif
----- Original Message -----
> On Friday, September 18, 2015, Leif Jensen <leif(at)crysberg(dot)dk> wrote:
>
> > Hello Laurenz,
> >
> > Thank you for you suggestion. I really want to aviod that someone
> > 'accidentally' deletes too much by typing (programming) a not full
> > qualified DELETE ... statement. In your case one would have to always use
> > the delete function, but no restrictions on using the DELETE statement.
> >
> >
> There is no way you can prevent a superuser from shooting themselves in the
> foot. For anyone else you can enforce use of the function to perform the
> delete.
>
> You could make a field called ok-to-delete and add a partial unique index
> on it so that only a single record can be marked ok to delete at a time and
> then have your trigger abort if it tries to delete a field without the ok
> to delete field set to true.
>
> David J.
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2015-09-18 13:16:03 | Re: Broken primary key after backup restore. |
| Previous Message | David G. Johnston | 2015-09-18 12:47:15 | Re: Delete trigger |