Dan Shearer

This was really interesting to find. I had not heard of SQLeet, and many of the problems SQLeet has are the same ones we have at LumoSQL, see https://lumosql.org/src/lumosql/doc/trunk/README.md ....

This is a fairly long answer with lots of links, but you did ask a very general question. It's also a very good question. > are you using the LumoSQL...

Ok that's a very fair point. It's time Fossil became a grown-up package!

> 5 requests a minute is, to say the least, not great ([see this wiki](https://rationalwiki.org/wiki/Internet_Archive#Restrictions)). > > Will try to look at some mitigation options (updating default concurrency, perhaps add...

> Could you outline what you mean by backend muxer? or is it intended as a descriptive to multiple interleaved transactions? This has evolved quite a bit. But as things...

> finish the initiatives for database and > source code for the past year. > > 1. move key payload from tail of key to new field in keyslot >...

Ok I see it: https://github.com/malbrain/database/tree/master/alpha . Dan

I am investigating full-service mirroring to Codeberg, and this might be relevant to your own work: https://codeberg.org/Recommendations/Mirror_to_Codeberg . I can confirm that the migration seems to work very well, but...

Hello @emansom , yes it has, in the sense that we have figured out how to do it, and the resulting databases appear to work with standard SQlite without any...

Oh it is certainly a timeout issue. But I was thinking that really this should be caught and presented as an error, and potentially even a back off and retry?...