Re: naming triggers for execution

From: Michael Nolan <htfoot(at)gmail(dot)com>
To: PegoraroF10 <marcos(at)f10(dot)com(dot)br>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: naming triggers for execution
Date: 2019-11-15 14:49:50
Message-ID: CAOzAqu+dTGDH50YfOyt7HcKekxEPZt=HQ3pRk4g8yFXRyGuZWQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> Considering that the auditing needs to be the last, how can I be sure it´ll
> ran lastly ?
>

IMHO, auditing should be done in after- triggers, when that the data in the
records being inserted, updated or deleted can't be changed but you can
still write to the separate auditing tables.
--
Mike Nolan

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2019-11-15 14:55:17 Re: Query which shows FK child columns?
Previous Message PegoraroF10 2019-11-15 14:31:09 naming triggers for execution