File tree Expand file tree Collapse file tree 1 file changed +3
-3
lines changed Expand file tree Collapse file tree 1 file changed +3
-3
lines changed Original file line number Diff line number Diff line change @@ -12,7 +12,7 @@ The KVStores are stored in the following structure in the KV db. Note that
12
12
the `perm` and `temp` buckets are identical in structure. The only difference
13
13
is that the `temp` bucket is cleared on restart of the db. The reason persisting
14
14
the temporary store changes instead of just keeping an in-memory store is that
15
- we can then guarantee idempotency if changes are made to both the permanent and
15
+ we can then guarantee atomicity if changes are made to both the permanent and
16
16
temporary stores.
17
17
18
18
rules -> perm -> rule-name -> global -> {k:v}
@@ -86,14 +86,14 @@ type KVStoreTx interface {
86
86
// GlobalTemp is similar to the Global store except that its contents
87
87
// is cleared upon restart of the database. The reason persisting the
88
88
// temporary store changes instead of just keeping an in-memory store is
89
- // that we can then guarantee idempotency if changes are made to both
89
+ // that we can then guarantee atomicity if changes are made to both
90
90
// the permanent and temporary stores.
91
91
GlobalTemp () KVStore
92
92
93
93
// LocalTemp is similar to the Local store except that its contents is
94
94
// cleared upon restart of the database. The reason persisting the
95
95
// temporary store changes instead of just keeping an in-memory store is
96
- // that we can then guarantee idempotency if changes are made to both
96
+ // that we can then guarantee atomicity if changes are made to both
97
97
// the permanent and temporary stores.
98
98
LocalTemp () KVStore
99
99
}
You can’t perform that action at this time.
0 commit comments