6 commits

Author	SHA1	Message	Date
Jackson Harper	c47a720fe4	Do not cache on write, so the most updated item is always available on read ... This is mostly an issue on tests where all the queries can be run in a single process, but if we cache on write, it means the next read will just have the cached value, instead of the calculated maximum value.	2024-02-01 09:59:42 +08:00
Jackson Harper	a060aaf496	Make reading position parsing safer	2024-02-01 09:59:42 +08:00
Jackson Harper	a40f5bed55	Create a service for interacting with cached read positions	2024-02-01 09:59:41 +08:00
Jackson Harper	fbfa934479	Write behind reading progress as a list that can be reduced at commit or read time	2024-02-01 09:59:39 +08:00
Jackson Harper	c2327781e1	Remove empty ctor	2024-02-01 09:57:11 +08:00
Jackson Harper	86c80d991f	Write behing cache for reading progress	2024-02-01 09:57:11 +08:00