Post #3912919
2026-07-18 13:09 UTC
Replies (4)
-
@bradlarsen@infosec.exchange 2026-07-18 14:48
@b0rk@social.jvns.ca in large part osmosis from poring over sqlite docs, reading more general database performance guides (like https://use-the-index-luke.com/), and then experimenting a lot with writing more complex queries in some apps I was working on. Having a high-level understanding of how joins are done and how a database uses available indexes helps tremendously. My main us of query planning: answering whether "this query will take forever" or if it will be fast. For my usual work (analytic workloads) there is usually no in-between.
-
@davecb@hachyderm.io 2026-07-18 13:11
@b0rk@social.jvns.ca I can't speak to sqlite, but I could only read Oracle plans if I first made a map of the fields I used, and how they would be searched. My DBA could do that all in his head (:-))
-
@kitten_tech@fosstodon.org 2026-07-18 13:25
@b0rk@social.jvns.ca I think all I know came from here: https://sqlite.org/eqp.html
-
@ednl@mastodon.social 2026-07-18 13:32
@b0rk@social.jvns.ca "Explain query" is new to me. https://www.sqlite.org/eqp.html Do you (does one) use it to look for optimisations of the table layout/keys/indices? Seems like a useful tool for complicated queries. I'm not a db designer anymore. When I was I had to rely on my Databases semester where we used this book: