Fossil SCM
Micro-touchups to the is-not-relational doc. (Its name really should be shortened to not-relational.md, but we already have links to the longer name out in the wild.)
Commit
213160c70c40124a1689fcc3bdc8867effed3de890a1b3c841f03a01c6caeb6b
Parent
7ebe73ff9a74fcc…
1 file changed
+5
-5
+5
-5
| --- www/fossil-is-not-relational.md | ||
| +++ www/fossil-is-not-relational.md | ||
| @@ -6,11 +6,11 @@ | ||
| 6 | 6 | unfamiliar with its internals to assume that Fossil stores its |
| 7 | 7 | SCM-relevant data in a database-friendly way and that the SCM history |
| 8 | 8 | can be modified via SQL. The truth, however, is *far stranger than |
| 9 | 9 | that.* |
| 10 | 10 | |
| 11 | -This presentation introduces, at a relatively high level: | |
| 11 | +This document introduces, at a relatively high level: | |
| 12 | 12 | |
| 13 | 13 | 1) The underlying enduring and immutable data format, which is |
| 14 | 14 | independent of any specific storage engine. |
| 15 | 15 | |
| 16 | 16 | 2) The `blob` table: Fossil's single point of SCM-relevant data |
| @@ -180,11 +180,11 @@ | ||
| 180 | 180 | R 74a0432d81b956bfc3ff5a1a2bb46eb5 |
| 181 | 181 | U drh |
| 182 | 182 | Z c9dcc06ecead312b1c310711cb360bc3 |
| 183 | 183 | ``` |
| 184 | 184 | |
| 185 | -Each line is a single data record called a "card". The first letter of | |
| 185 | +Each line is a single data record called a "card." The first letter of | |
| 186 | 186 | each line tells us the type of data stored on that line and the |
| 187 | 187 | following space-separated tokens contain the data for that |
| 188 | 188 | line. Tokens which themselves contain spaces (notably the checkin |
| 189 | 189 | comment) have those escaped as `\s`. The raw text of wiki |
| 190 | 190 | pages/comments, forum posts, and ticket bodies/comments is stored |
| @@ -397,10 +397,10 @@ | ||
| 397 | 397 | |
| 398 | 398 | - **Two-way compatibility with other hypothetical clients** which also |
| 399 | 399 | implement the same underlying data model. So far there are none, but |
| 400 | 400 | it's conceivably possible. |
| 401 | 401 | |
| 402 | -- **Provides a solid basis for reporting.** Fossil's metrics and | |
| 403 | - reporting options are arguably the most powerful and flexible yet | |
| 404 | - seen in an SCM. | |
| 402 | +- **Provides a solid basis for reporting.** Fossil's real-time metrics | |
| 403 | + and reporting options are arguably the most powerful and flexible | |
| 404 | + yet seen in an SCM. | |
| 405 | 405 | |
| 406 | 406 | - Very probably several more things. |
| 407 | 407 |
| --- www/fossil-is-not-relational.md | |
| +++ www/fossil-is-not-relational.md | |
| @@ -6,11 +6,11 @@ | |
| 6 | unfamiliar with its internals to assume that Fossil stores its |
| 7 | SCM-relevant data in a database-friendly way and that the SCM history |
| 8 | can be modified via SQL. The truth, however, is *far stranger than |
| 9 | that.* |
| 10 | |
| 11 | This presentation introduces, at a relatively high level: |
| 12 | |
| 13 | 1) The underlying enduring and immutable data format, which is |
| 14 | independent of any specific storage engine. |
| 15 | |
| 16 | 2) The `blob` table: Fossil's single point of SCM-relevant data |
| @@ -180,11 +180,11 @@ | |
| 180 | R 74a0432d81b956bfc3ff5a1a2bb46eb5 |
| 181 | U drh |
| 182 | Z c9dcc06ecead312b1c310711cb360bc3 |
| 183 | ``` |
| 184 | |
| 185 | Each line is a single data record called a "card". The first letter of |
| 186 | each line tells us the type of data stored on that line and the |
| 187 | following space-separated tokens contain the data for that |
| 188 | line. Tokens which themselves contain spaces (notably the checkin |
| 189 | comment) have those escaped as `\s`. The raw text of wiki |
| 190 | pages/comments, forum posts, and ticket bodies/comments is stored |
| @@ -397,10 +397,10 @@ | |
| 397 | |
| 398 | - **Two-way compatibility with other hypothetical clients** which also |
| 399 | implement the same underlying data model. So far there are none, but |
| 400 | it's conceivably possible. |
| 401 | |
| 402 | - **Provides a solid basis for reporting.** Fossil's metrics and |
| 403 | reporting options are arguably the most powerful and flexible yet |
| 404 | seen in an SCM. |
| 405 | |
| 406 | - Very probably several more things. |
| 407 |
| --- www/fossil-is-not-relational.md | |
| +++ www/fossil-is-not-relational.md | |
| @@ -6,11 +6,11 @@ | |
| 6 | unfamiliar with its internals to assume that Fossil stores its |
| 7 | SCM-relevant data in a database-friendly way and that the SCM history |
| 8 | can be modified via SQL. The truth, however, is *far stranger than |
| 9 | that.* |
| 10 | |
| 11 | This document introduces, at a relatively high level: |
| 12 | |
| 13 | 1) The underlying enduring and immutable data format, which is |
| 14 | independent of any specific storage engine. |
| 15 | |
| 16 | 2) The `blob` table: Fossil's single point of SCM-relevant data |
| @@ -180,11 +180,11 @@ | |
| 180 | R 74a0432d81b956bfc3ff5a1a2bb46eb5 |
| 181 | U drh |
| 182 | Z c9dcc06ecead312b1c310711cb360bc3 |
| 183 | ``` |
| 184 | |
| 185 | Each line is a single data record called a "card." The first letter of |
| 186 | each line tells us the type of data stored on that line and the |
| 187 | following space-separated tokens contain the data for that |
| 188 | line. Tokens which themselves contain spaces (notably the checkin |
| 189 | comment) have those escaped as `\s`. The raw text of wiki |
| 190 | pages/comments, forum posts, and ticket bodies/comments is stored |
| @@ -397,10 +397,10 @@ | |
| 397 | |
| 398 | - **Two-way compatibility with other hypothetical clients** which also |
| 399 | implement the same underlying data model. So far there are none, but |
| 400 | it's conceivably possible. |
| 401 | |
| 402 | - **Provides a solid basis for reporting.** Fossil's real-time metrics |
| 403 | and reporting options are arguably the most powerful and flexible |
| 404 | yet seen in an SCM. |
| 405 | |
| 406 | - Very probably several more things. |
| 407 |