Mutating the db creates a cycle. Search for e/offload in the channel for previous discussions

Yes! e/snapshot worked for me - I'll use that as a workaround until UI5 obsoletes it. I don't understand e/offload, on an ELI5 level, does it effectively run something asynchronously? (while letting you optimise for the type of bottleneck you expect)

Don't worry, I found a quote: "`e/offload` moves a blocking computation to a threadpool (see docstring), so as not to block the reactive computation. databases are slow and blocking (even transact) so all database operations must be offloaded" 👍

I don’t see how offload prevents cycles without combining with snapshot. Or if it does, it raises other questions, like how come reactive updates to queries using db as input works?

I meant to write e/snapshot. Shows why replying at night is not a great idea