From 3ed4d87396961786df9d87f978f35f9ac3d7badf Mon Sep 17 00:00:00 2001 From: Matthias Eckert Date: Mon, 6 Mar 2023 15:23:24 +0100 Subject: [PATCH] [logseq-plugin-git:commit] 2023-03-06T14:23:23.805Z --- journals/2023_03_06.md | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/journals/2023_03_06.md b/journals/2023_03_06.md index 9ab0127e..4c41b039 100644 --- a/journals/2023_03_06.md +++ b/journals/2023_03_06.md @@ -27,4 +27,11 @@ - a bargain price - in a bulk = make supplies of - limited edition flavours -- https://www.chefkoch.de/rezepte/1481031253346883/Schwaebischer-Salzkuchen.html [[Rezepte]] \ No newline at end of file +- https://www.chefkoch.de/rezepte/1481031253346883/Schwaebischer-Salzkuchen.html [[Rezepte]] +- API Questions: + - What guarantees are given on the data on the events endpoint? Is ID increasing all the time (in increments of 1)? + - + - What about the missing event ID 119434986? Is that a bug or can events have missing IDs in the increasing series? + - What is createdAt referring to? (I assumed it’s the time the event happened, but then later IDs should have higher timestamps) Why can it be decreasing in events with later IDs. How does it relate to the document timestamps (we established in earlier conversations that document updatedAt can differ from event createdAt because they are different processes) + - How am I supposed to know if I got all events if there are missing ones and timestamps and/or IDs are not monotonically increasing? + - Also if you replay events, do you also replay data, so is e.g. document 7a233a97-1f18-3792-b287-c7b35f601f0b also not yet updated on the documents endpoint and we need to wait 15 minutes from some timestamp (in that case no idea how to figure that out instead of retrying for some time) for this to update? \ No newline at end of file