Abstract: A method of reducing the time taken to manufacture a bitemporal relational database is disclosed. The method involves designing business database tables with relational rules stored in a relational kernel or referential rule dictionary, and designing those tables so as to be without start date and end date columns for start of valid time and end of valid time for entities, and designing the system to be without history tables recording the history of relationships between entities in the database; the system being designed as a current view with primary key and unique key constraints, and time-related issues being taken care of by the S$, T$, and E$ tables automatically generated as the data structure of the system is populated with data.

Abstract: A method of reducing the time taken to manufacture a bitemporal relational database is disclosed. The method involves designing business database tables with relational rules stored in a relational kernel or referential rule dictionary, and designing those tables so as to be without start date and end date columns for start of valid time and end of valid time for entities, and designing the system to be without history tables recording the history of relationships between entities in the database; the system being designed as a current view with primary key and unique key constraints, and time-related issues being taken care of by the S$, T$, and E$ tables automatically generated as the data structure of the system is populated with data.

Abstract: A database having data entries with attributes having values that can vary over system time (the time according to a computer clock) and also over valid time (the start time and end time of an interval during which the values of the attributes are true). All logical operations of updates and deletes of values are performed by insert operations that insert new entries into the database, so that all old entries that were present at previous systems still exist and still include their previously-assigned start times and end times for the value of the attribute.

Abstract: A database having data entries with attributes having values that can vary over system time (the time according to a computer clock) and also over valid time (the start time and end time of an interval during which the values of the attributes are true). All logical operations of updates and deletes of values are performed by insert operations that insert new entries into the database, so that all old entries that were present at previous systems still exist and still include their previously-assigned start times and end times for the value of the attribute.

Abstract: A database having data entries with attributes having values that can vary over system time (the time according to a computer clock) and also over valid time (the start time and end time of an interval during which the values of the attributes are true). All logical operations of updates and deletes of values are performed by insert operations that insert new entries into the database, so that all old entries that were present at previous systems still exist and still include their previously-assigned start times and end times for the value of the attribute.

Abstract: A database having data entries with attributes having values that can vary over system time (the time according to a computer clock) and also over valid time (the start time and end time of an interval during which the values of the attributes are true). All logical operations of updates and deletes of values are performed by insert operations that insert new entries into the database, so that all old entries that were present at previous system times still exist and still include their previously-assigned start times and end times for the value of the attribute.

Abstract: In one embodiment, a method of providing data entities of a database with a time dependent value for an attribute of the entity is disclosed.