Re: How to ensure a log-entry is created based on state of data in other tables

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Andreas Joseph Krogh <andreas(at)visena(dot)com>
Cc: pgsql-sql(at)lists(dot)postgresql(dot)org
Subject: Re: How to ensure a log-entry is created based on state of data in other tables
Date: 2023-02-09 16:44:25
Message-ID: CAKFQuwYuYs0nmWpgLUwfTP5pF7zZgxJP+BqFj8gToZ4=RH89SQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-sql

On Thu, Feb 9, 2023 at 12:24 AM Andreas Joseph Krogh <andreas(at)visena(dot)com>
wrote:

> Is there a better way, using some extra tables to do bookkeeping can the
> have constraints ensuring this business-requirement?
>
>
>
Every time an activity newly becomes "Not Done" increment a "not done seen
counter" and likewise with a "done seen counter". Whenever the former is
greater than the later you have one or more not done activities.

David J.

In response to

Responses

Browse pgsql-sql by date

  From Date Subject
Next Message Rob Sargent 2023-02-09 16:44:38 Re: How to ensure a log-entry is created based on state of data in other tables
Previous Message Steve Midgley 2023-02-09 16:37:35 Re: How to ensure a log-entry is created based on state of data in other tables