| From: | Andreas Joseph Krogh <andreas(at)visena(dot)com> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(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:59:03 |
| Message-ID: | VisenaEmail.6b.d76438498ddf3620.186371b8050@visena.app.internal.visena.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
På torsdag 09. februar 2023 kl. 17:44:25, skrev David G. Johnston <
david(dot)g(dot)johnston(at)gmail(dot)com <mailto:david(dot)g(dot)johnston(at)gmail(dot)com>>:
On Thu, Feb 9, 2023 at 12:24 AM Andreas Joseph Krogh <andreas(at)visena(dot)com
<mailto: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.
Ah, this is what I'm looking for, I think.
--
Andreas Joseph Krogh
CTO / Partner - Visena AS
Mobile: +47 909 56 963
andreas(at)visena(dot)com <mailto:andreas(at)visena(dot)com>
www.visena.com <https://www.visena.com>
<https://www.visena.com>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | michele curioni | 2023-02-23 21:18:20 | Could not serialize access due to read/write dependencies among transactions |
| Previous 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 |