> On Jan 4, 2021, at 11:06, Dirk Mika <dirk.m...@mikatiming.de> wrote:
>
> See thread below:
>
> https://www.postgresql.org/message-id/VisenaEmail.26.7cbf2947c8d23ceb.1769a2755ff%40tc7-visena
>
> I found that thread already, but It doesn't not provide a solution to my
> problem.
One possibility, which is admittedly very hacky, is:
-- Create a new column which is a flag (or bitmap) of other columns that need
to be managed in this way, with a default of 0.
-- Have two EACH ROW triggers:
* The first is ON UPDATE OF the actual column to managed, and sets the
appropriate flag or bitmap in the flag column when run. This flags that the
application has updated the column.
* The second, which runs always, checks that flag, and if it is set, clears it;
otherwise, it sets the column to the value desired if the application didn't
change it.
Of course, the order of execution of these triggers matters; PostgreSQL
executes triggers at the same level alphabetically.
Now, this is a pretty high-overhead way of handling it, and it is probably
better to see if there is an application logic change that can happen here.
Best,
--
-- Christophe Pettus
x...@thebuild.com
