Talk:Bitemporal modeling

Missing “future” change rollout use
IT folk don’t like to “bring systems down” & “load up” rows at say, midnight New Year’s Eve. Having new “offers” or “products” roll out in future may be inserted or fixed or changed or renamed or deleted or rolled-out/back if an “oops” at some point-of-consistency across applications teams at point-in-time planned and pre-agreed to in future using bi-temporal features & functionality & capabilities in almost all RDBMSes this century.

Trends over time need “event” impacts 2600:1700:62E0:2BC0:119:1FF2:1199:2E11 (talk) 06:53, 18 April 2023 (UTC)