From 4ffa35addf822e24c387cfff79b9dd1a81f91ac6 Mon Sep 17 00:00:00 2001 From: Evan Cordell Date: Wed, 11 Oct 2023 16:11:07 -0400 Subject: [PATCH] fix list formatting in crdb overlap doc --- internal/datastore/crdb/README.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/internal/datastore/crdb/README.md b/internal/datastore/crdb/README.md index 94a01d1ea7..cf32916f9d 100644 --- a/internal/datastore/crdb/README.md +++ b/internal/datastore/crdb/README.md @@ -60,8 +60,8 @@ Let's take a look at a couple of examples of how reversed timestamps may be an i Two separate `WriteRelationship` calls come in: -`A`: Alice removes Bob from the `shared` folder -`B`: Alice adds a new document `not-for-bob.txt` to the `shared` folder +- `A`: Alice removes Bob from the `shared` folder +- `B`: Alice adds a new document `not-for-bob.txt` to the `shared` folder The normal case is that the timestamp for `A` < the timestamp for `B`. @@ -88,9 +88,9 @@ This could be mitigated in your application by: Two separate API calls come in: -`A`: Alice remove Bob as a viewer of document `secret` -`B`: Alice does a `FullyConsistent` `Check` request to get a ZedToken -`C`: Alice stores that ZedToken (timestamp `B`) with the document `secret` when she updates it to say `Bob is a fool`. +- `A`: Alice remove Bob as a viewer of document `secret` +- `B`: Alice does a `FullyConsistent` `Check` request to get a ZedToken +- `C`: Alice stores that ZedToken (timestamp `B`) with the document `secret` when she updates it to say `Bob is a fool`. Same as before, the normal case is that the timestamp for `A` < the timestamp for `B`, but if the two writes hit the conditions for a timestamp reversal, then `B < A`.