dbeaver VS dqlite

Yes but not in the community version:

https://github.com/dbeaver/dbeaver/wiki/Schema-compare

DBeaver is a veteran SQL client. In addition to basic visualization and management capabilities, it has a SQL editor, data and schema migration capabilities, monitor database connections, and more. It supports a full range of databases (both SQL and NoSQL). DBeaver is also hooked up with GPT-3, which converts your natural language to SQL.

If you want to do something meaningful, here's the DBeaver GitHub repo https://github.com/dbeaver/dbeaver. Go contribute a ChatGPT plugin & update the UI to look nicer.

dbeaver is an excellent option as well, plus it supports basically every kind of SQL database in existence.

Curiously enough, just yesterday a snap broke on me. People on the github thread said reverting snap didn't work either - I'm not sure whether they simply couldn't revert, or they reverted and still had issues, as I just saw this and slapped on the flatpak instead of messing with my snap. I'm also not sure whether the snap revert didn't work because of something the dbeaver team screwed up there as well, however I'll make sure to avoid automatic/unattended updates in the future. I'm running Arch on my personal machine anyway, so it's not like I mind running updates regularly, but I'd rather do it at my own discretion.

Please create a ticket and describe your issue here: https://github.com/dbeaver/dbeaver/issues/new/choose

I did find https://github.com/dbeaver/dbeaver/issues/6064 marked as closed, perhaps that will help?

If you're interested in this, here are some related projects that all take slightly different approaches:

- LiteSync directly competes with Marmot and supports DDL sync, but is closed source commercial (similar to SQLite EE): https://litesync.io

- dqlite is Canonical's distributed SQLite that depends on c-raft and kernel-level async I/O: https://dqlite.io

- cr-sqlite is a Rust-based loadable extension that adds CRDT changeset generation and reconciliation to SQLite: https://github.com/vlcn-io/cr-sqlite

Slightly related but not really (no multi writer, no C-level SQLite API or other restrictions):

- comdb2 (Bloombergs multi-homed RDMS using SQLite as the frontend)

- rqlite: RDMS with HTTP API and SQLite as the storage engine, used for replication and strong consistency (does not scale writes)

- litestream/LiteFS: disaster recovery replication

- liteserver: active read-only replication (predecessor of LiteSync)

I'd be curious for a similar tuning with Dqlite: https://github.com/canonical/dqlite

Anyone knows how the DB this is about, https://rqlite.io/, compares with https://dqlite.io/ by Canonical (both seem to be distributed versions of sqlite)?

For folks' context, the new tool that's being discussed in the thread mentioned by the parent here is litefs [0], as well as which you can also look at rqlite [1] and dqlite [2], which all provide different trade-offs (e.g. rqlite is 'more strongly consistent' than litefs).

[0]: https://github.com/superfly/litefs

[1]: https://github.com/rqlite/rqlite

[2]: https://github.com/canonical/dqlite

I presume you're familiar with https://github.com/canonical/dqlite (made by my employer) and https://github.com/rqlite/rqlite (unrelated)? How will mvsqlite compare to those?

Check out dqlite, it's sqlite but with a raft consensus to distribute changes through a log: https://dqlite.io/ You can link it in as a library too, it sounds like exactly what you want.