The home page doesn't say what it actually is or does.
Main thing seems to be pluggable backends.
LumoSQL
51–60 of 90 posts
Re: LumoSQL
#52The home page doesn't say what it actually is or does.
The home page says, "LumoSQL can swap back end key-value store engines in and out of SQLite. LMDB is the most famous (but not the only) example of an alternative key-value store, and LumoSQL can combine dozes of versions of LMDB and SQLite source code(...)" and also, "Encryption and corruption detection, optionally per-row".
Re: LumoSQL
#53The home page doesn't say what it actually is or does.
The home page says, "LumoSQL can swap back end key-value store engines in and out of SQLite. LMDB is the most famous (but not the only) example of an alternative key-value store, and LumoSQL can combine dozes of versions of LMDB and SQLite source code(...)" and also, "Encryption and corruption detection, optionally per-row".
"LumoSQL can swap back end key-value store engines in and out of SQLite."
=>
"LumoSQL can swap SQLite backend, with Key-value store engines"
===
"LMDB is the most famous (but not the only) example of an alternative key-value store"
=>
"We currently only support LMDB as an alternative KV store"
===
"and LumoSQL can combine dozes of versions of LMDB and SQLite source code like this:"
=>
"LumoSQL will allow you to use different versions of SQLite and LMDB in parallel as different backends"
Re: LumoSQL
#54AFAIR, LMDB is very buggy. There was one person who showed that and maintained fork of LMDB with many bugs fixed, but he is very opinionated and think that world outside Russia is "evil" and forbid to use his fork for evil...
Oh, license was changed to Apache 2.0! But still github account has note which equals Hitler to Soros...
Why should SQLite backend be replaced with LMDB?
UPD: Ooops, LMDB was forked a long time ago, so, maybe, LMDB can be fixed already!
Re: LumoSQL
#55Earlier quoted context omitted.
The home page says, "LumoSQL can swap back end key-value store engines in and out of SQLite. LMDB is the most famous (but not the only) example of an alternative key-value store, and LumoSQL can combine dozes of versions of LMDB and SQLite source code(...)" and also, "Encryption and corruption detection, optionally per-row".
"LumoSQL can swap back end key-value store engines in and out of SQLite." => "LumoSQL can swap SQLite backend, with Key-value store engines" === "LMDB is the most famous (but not the only) example of an alternative key-value store" => "We currently only support LMDB as an alternative KV store" === "and LumoSQL can combine dozes of versions of LMDB and SQLite source code like this:" => "LumoSQL will allow you to use d…
Why are you reposting these sentences with additional errrors inserted into them?
Re: LumoSQL
#56Can LumoSQL be used with Litestream for replication?
Re: LumoSQL
#57How does LumoSQL compare to LibSQL/Turso?
Re: LumoSQL
#58Possibly the wrong place to ask this, but: I've played with SQLite when it was still available in-browser, and I felt that was on the brink of being a game-changer. If it was still supported in-browser and we had replication from the browser, peer-to-peer, I think we'd be living in a much more useful world. It's a lovely tech, but I never built anything serious around it. At this point, as a front-end web technology…
Two things: 1. There's almost certainly a port of Sqlite3 to WASM that would be more than glad to run in your browser. 2. I'd really love to know what applications fit in the "we had replication from the browser, peer-to-peer, I think we'd be living in a much more useful world" situation. We've had GunDB, IPFS, etc. that live in the browser for decades (and projects like Urbit), and the killer app just... doesn't see…
Re: LumoSQL
#59SQLite itself is open source, but the last time I checked, its test suite remains proprietary. How does a "fork" like this be tested if everything stays working and compatible to upstream after the change?
The general test suite is not proprietary, and is a standard part of the code. You can run make test. It uses TCL to run the testing, and covers virtually everything. There is a separate TH3 test suite which is proprietary. It generates C code of the tests so you can run the testing in embedded and similar environments, as well as coverage of more obscure test cases. https://sqlite.org/th3.html
Why is that? Surely that leads to conversations with open source contributors like 'this fails the test suite, but I can't show you, please fix it'?
Re: LumoSQL
#60Earlier quoted context omitted.
I'm confused, is this just patch and apply patch?
Yes. It's a small DSL to fork a repository and apply a series of textfile transformations (replace file, replace partial file). But if you give this a cool name, it's a New Idea.
So it's a fork but with somewhat semantic diff specifications?