Talk:Bitemporal modeling

Computing Low‑importance

	This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing articles
Low	This article has been rated as Low-importance on the project's importance scale.

Databases (inactive)

This article is within the scope of WikiProject Databases, a project which is currently considered to be inactive.DatabasesWikipedia:WikiProject DatabasesTemplate:WikiProject DatabasesDatabases articles

Missing “future” change rollout use

Latest comment: 1 year ago1 comment1 person in discussion

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

Add topic