 |
See also: https://en.wikipedia.org/wiki/Temporal_database https://mariadb.com/kb/en/library/system-versioned-tables/ |
|
|
From the temporal page on wikipedia: "..Valid time is the time for which a fact is true in the real world. A valid time period may be in the past, span the current time, or occur in the future. For the example above, to record valid time, the Person table has two fields added, Valid-From and Valid-To. These specify the period when a person's address is valid in the real world. ..Transaction time records the time period during which a database entry is accepted as correct. This enables queries that show the state of the database at a given time. Transaction time periods can only occur in the past or up to the current time. In a transaction time table, records are never deleted. Only new records can be inserted, and existing ones updated by setting their transaction end time to show that they are no longer current. To enable transaction time in the example above, two more fields are added to the Person table: Transaction-From and Transaction-To. Transaction-From is the time a transaction was made, and Transaction-To is the time that the transaction was superseded (which may be infinity if it has not yet been superseded). This makes the table into a bitemporal table..." |
|
|
Asserted time and State time: https://www.sciencedirect.com/topics/computer-science/asserted-versioning |
|
|
SQL2011 support: https://www.dummies.com/programming/sql/how-to-track-data-with-sql2011-bitemporal-tables/ |
|
|
Closing automatically, stayed too long in resolved state. Feel free to re-open with additional information if you think the issue is not resolved. |
- Anonymous
