From bbaa300aabbefaf1fdef2dd412b991ba65c3c54e Mon Sep 17 00:00:00 2001 From: Paul d'Aoust Date: Thu, 28 Mar 2024 15:55:34 -0700 Subject: [PATCH] update SVGs -- they don't look right tho --- src/pages/build/guide/entries.md | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/src/pages/build/guide/entries.md b/src/pages/build/guide/entries.md index 058ed1b2f..b6c10182b 100644 --- a/src/pages/build/guide/entries.md +++ b/src/pages/build/guide/entries.md @@ -199,12 +199,16 @@ Holochain gives you this `update_entry` function, but is somewhat unopinionated You can also choose where to attach updates. You can structure them as a 'list', where all updates refer to the `ActionHash` of the original `Create` action. -
Update 1
Create
Update 2
Update 3
Update 4
 + +
Update 1
Create
Update 2
Update 3
Update 4
 Or you can structure your updates as a 'chain', where each update refers to the `ActionHash` of the previous entry creation action (either an `Update` or the original `Create`). - -
Update 1
Create
Update 2
Update 3
Update 4
 + +
Update 1
Create
Update 2
Update 3
Update 4
 If you structure your updates as a chain, you may want to also create links from the `ActionHash` of the original `Create` to each update in the chain, making it a hybrid of a list and a chain. This trades additional storage space for reduced lookup time.