36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
|
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
|
-
+
+
|
An artifact is a list of bytes - a "file" in the usual manner of thinking.
Many artifacts are simply the content of source files that have
been checked into the Fossil repository. Call these "content artifacts".
Other artifacts, known as
"control artifacts", contain ASCII text in a particular format that
defines relationships between other artifacts, such as which
content artifacts that go together to form a particular version of the
project. Each artifact is named by its SHA1 hash and is thus immutable.
project. Each artifact is named by its SHA1 or SHA3-256 hash and is
thus immutable.
Artifacts can be added to the database but not removed (if we ignore
the exceptional case of [./shunning.wiki | shunning].) Repositories
synchronize by computing the union of their artifact sets. SQL and
relation theory play no role in any of this.
SQL enters the picture only in the implementation details. The current
implementation of Fossil stores each artifact as a BLOB in an SQLite
|