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

På torsdag 09. februar 2023 kl. 16:08:16, skrev Steve Midgley <
science(at)misuse(dot)org <mailto:science(at)misuse(dot)org>>:

[…]

What is the time window required for "DONE" and "NOT_DONE" to be correct? Do
they need to be atomic (meaning the time window is effectively 0)? Or can the
system "notice" recent changes and keep track of done/not done after-the-fact?
If your time window is > 0, it seems like recurring processes could be set up
to track DONE / NOT_DONE?

Another totally different way to think about this is to create a view that
provides answers on DONE and NOT_DONE as computed values based on the
underlying state of the table at the time the view is queried? That would seem
to satisfy a time window of 0?

Steve
Yes, they need to be atomic. Either all are DONE and there is an entry in
activity_product_log for product_id, or there is no entry in
activity_product_log.

--
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>