Awesome!
I've been wishing something like FDB's record-layer w/o Java/JVM and this has a lot of potential.<p>I have a question though- How does it handle conflicts within a sqlite DB and among multiple sqlite DBs?<p>I believe FDB maintains strict serializability by detecting conflicts among concurrent transactions by checking conflict ranges.<p>I read the doc and the mvstore code and perhaps it's working by writing the deltas of changed pages with the read version obtained at the sqlite transaction creation?<p>If that's the case, I'm still unsure what you added to the conflict ranges other than the deltas of the pages.
To make it actually serializable, you'd need to add conflict ranges for all the pages that are `select`ed within the sqlite transaction?