From 8ac9f3891b178a406550bf73bf5ab99fc4ccdef5 Mon Sep 17 00:00:00 2001 From: Nick Alexander Date: Tue, 7 Feb 2017 12:14:13 -0800 Subject: [PATCH] Updated Transacting: upsert resolution algorithm (markdown) --- Transacting:-upsert-resolution-algorithm.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Transacting:-upsert-resolution-algorithm.md b/Transacting:-upsert-resolution-algorithm.md index 5389e9f..c12188f 100644 --- a/Transacting:-upsert-resolution-algorithm.md +++ b/Transacting:-upsert-resolution-algorithm.md @@ -20,7 +20,7 @@ We partition the set of transaction entities into the following populations. | `upserts-ev` | "Complex upserts" that look like `[:db/add -1 a -2]` where `a` is `:db.unique/identity` | | `allocations-ev` | Entities that look like `[:db/add -1 b -2]`, where `b` is *not* `:db.unique/identity` | | `allocations-e` | Entities that look like `[:db/add -1 b v]`, where `b` is *not* `:db.unique/identity` | -| `allocations-v` | Entities that look like `[:db/add e b -2]`, where `b` is *not* `:db.unique/identity` | +| `allocations-v` | Entities that look like `[:db/add e b -2]`, with no condition on `b` | | `inert` | Entities that are not `[:db/add ...]`, or that do not contain a temporary ID, like `[:db/add e a v]` | ## Evolutionary step