GlcoinCore/lightning-terminal
1
0
Fork 0
mirror of https://github.com/lightninglabs/lightning-terminal.git synced 2026-08-13 12:33:36 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions 2

firewalldb: address last few comments from #763

Browse source
This commit is contained in:
Elle Mouton 2024-06-06 12:49:35 -04:00
parent 33d717a624
commit 5e07588b43
No known key found for this signature in database
GPG key ID: D7D916376026F177
1 changed files with 3 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

6
firewalldb/kvstores.go
View file

@ -12,7 +12,7 @@ The KVStores are stored in the following structure in the KV db. Note that
the `perm` and `temp` buckets are identical in structure. The only difference
is that the `temp` bucket is cleared on restart of the db. The reason persisting
the temporary store changes instead of just keeping an in-memory store is that
we can then guarantee idempotency if changes are made to both the permanent and
we can then guarantee atomicity if changes are made to both the permanent and
temporary stores.
rules -> perm -> rule-name -> global -> {k:v}
@ -86,14 +86,14 @@ type KVStoreTx interface {
// GlobalTemp is similar to the Global store except that its contents
// is cleared upon restart of the database. The reason persisting the
// temporary store changes instead of just keeping an in-memory store is
// that we can then guarantee idempotency if changes are made to both
// that we can then guarantee atomicity if changes are made to both
// the permanent and temporary stores.
GlobalTemp() KVStore
// LocalTemp is similar to the Local store except that its contents is
// cleared upon restart of the database. The reason persisting the
// temporary store changes instead of just keeping an in-memory store is
// that we can then guarantee idempotency if changes are made to both
// that we can then guarantee atomicity if changes are made to both
// the permanent and temporary stores.
LocalTemp() KVStore
}