Commit 9bcb1889 by Tom Laudeman

rename file

parent 568665c6
...@@ -22,12 +22,14 @@ create table version_history ( ...@@ -22,12 +22,14 @@ create table version_history (
The version_history table is the central table to a CPF constellation (aka record). The The version_history table is the central table to a CPF constellation (aka record). The
version_history.main_id is the constellation id. By convention, all SNAC tables have a field id, which is the version_history.main_id is the constellation id. By convention, all SNAC tables have a field id, which is the
record is. Field version_history.id is known by the alias "version" in all locations outside table record id. Field version_history.id is known by the alias "version" in all locations outside table
version_history. All first-order data tables have fields id,version, and main_id. It may help to understand version_history. All first-order data tables have fields id,version, and main_id. It may help to understand
some of the following specification by knowing that the unique record key for nearly all tables is some of the following specification by knowing that the unique record key for nearly all tables is
(id,version). For all tables except nrd, the constellation id is main_id. Table nrd is 1:1 data fields, and is (id,version). For all tables except nrd, the constellation id is main_id. Table nrd is 1:1 data fields, and is
special, therefore nrd.id is both record id and constellation id. special, therefore nrd.id is both record id and constellation id.
There are some basic traits of versioning There are some basic traits of versioning
1) No record is ever deleted. Old versions of every record are left in the database. 1) No record is ever deleted. Old versions of every record are left in the database.
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment