4d9e3e6 · project-m36 · git.iko.soy

git.iko.soy/project-m36

fix typos in various docs

commit4d9e3e6008a10df1aaf8e4fa62d3834f0309a463 authorAgentM <agentm@themactionfaction.com> dateMon 5 Oct 2015, 18:24 (11 years ago) parent424ab11

2 files changed+7−7

compare with master

unifiedsplit

docs/introduction_to_projectm36.markdown+4−4 docs/transaction_graph_operators.markdown+3−3

docs/introduction_to_projectm36.markdown+4−4

@@ -23,10 +23,10 @@ Requirements:

2323

2424Compilation steps:

2525

26−* git clone https://github.com/agentm/project-m36

27−* cd project-m36

28−* cabal sandbox init

29−* cabal install

26+* ```git clone https://github.com/agentm/project-m36```

27+* ```cd project-m36```

28+* ```cabal sandbox init``` (optional but recommended)

29+* ```cabal install```

3030

3131At this point, the TutorialD interactive interpreter can be run using ```cabal run tutd```.

3232

docs/transaction_graph_operators.markdown+3−3

@@ -1,4 +1,4 @@

1−## Transaction Operators

1+## Transaction Graph Operators

33Relational operators generate new relations and database context operators alter the relations referenced by relation variables. Finally, transaction operators alter the state of the database's transaction graph. This includes adding new transactions, branching, and changing the current database context to point at an arbitrary transaction in the past (time-travel).

@@ -10,7 +10,7 @@ When a new database is created, a new transaction graph is created for it with o

1010

1111As the user interactively alters the database context such as by adding a new relation variable, the database context is no longer equal to that of the first transactions. This is called "database context divergence" because many of the same components exist in both the updated context and the context of the first transaction.

1212

13−[Initial database starting state](http://g.gravizo.com/g?

13+![Initial database starting state](http://g.gravizo.com/g?

1414digraph G {

1515 base[label="base transaction",shape=rectangle];

1616 new[label="mutable database context"];

@@ -19,7 +19,7 @@ digraph G {

1919

2020Once the user decides that the changes in the updated database context are worth adding to the transaction graph, the user issues a "commit" request. The commit operation converts the current database context into a new transaction which is then added to the graph with the parent transaction set to the same parent transaction as the database context. The user's mutable database context is shifted to be a copy of the context of the newly-committed transaction.

2121

22−[Freshly committed transaction](http://g.gravizo.com/g?

22+![Freshly committed transaction](http://g.gravizo.com/g?

2323digraph G {

2424 base[label="base transaction",shape=rectangle];

2525 discon[label="mutable database context"];