sqlite3todot

Postgres is better in the I-need-concurrency case -- I think it's the greatest RDBMS that's ever been made and would like someone to prove me wrong some day. SQLite's amazing too though, when you don't need concurrency (and most websites don't really -- especially the ones that should be scaling vertically instead of horizontally). Anyway here's some cool SQLite stuff: - https://github.com/CanonicalLtd/dqlite - https://github.com/rqlite/rqlite - https://datasette.readthedocs.io/en/stable/ - https://www.sqlite.org/rtree.html - https://github.com/sqlcipher/sqlcipher - https://github.com/benbjohnson/litestream - https://github.com/aergoio/aergolite - https://sqlite.org/lang_with.html#rcex3 - https://github.com/sql-js/sql.js - https://www.gaia-gis.it/fossil/libspatialite/index - https://github.com/h3rald/litestore - https://github.com/adamlou

I implemented a DB visualisation tool like this for sqlite3, also using graphviz. It's called, unimaginatively, sqlite3todot [1] The couple tricks it has that I really like are a) it shows the table itself [which isn't uncommon], but also b) has the ability to group up tables, which for me turns out to be a devastatingly killer feature that no other tool has. When I'm working on a schema [especially one I've not seen before], one of the things that drives me insane is not being able to say "these six go together. Group them". Then you can simply look at arrows that enter or leave that grouping for your next exploration step. By the time I'm done, anything not-categorised stands out [it's simply in the space between groups]; any boxes that have an excess of arrows between them can mean my mental model is wrong [or the schema has some nonop