3 ms·
Looks similar to EXPLAIN QUERY PLAN: https://sqlite.org/eqp.html https://sqlite.org/eqp.html Raw EXPLAIN dumps bytecode, which is usually much more verbose tha
by inigyou 4mo ago
Looks similar to EXPLAIN QUERY PLAN: https://sqlite.org/eqp.html https://sqlite.org/eqp.html
Raw EXPLAIN dumps bytecode, which is usually much more verbose than you want. EXPLAIN QUERY PLAN dumps a summary.
- xetera 4mo agoIn my experience, SQLite explain plans are by far the most useless of any database out there. No concept of costing, no buffer information, no explain analyze. It's almost like they don't want you looking at it.
- inigyou 4mo agosqlite competes with fopen. If you don't like it, use a real database.
- simonw 4mo agoWhat's your criteria for a "real database"?
- deleted 4mo ago[deleted]
- antonvs 4mo agoA couple of obvious ones would be running as a standalone service, and supporting multiple concurrent writes. Both of these help support transparent handling of multiple concurrent clients, which seems like table stakes for a "real database".
- phil294 4mo ago...performance-wise. Not in general. It obviously does more than just opening a file. Also, you don't get to choose your competitors. SQLite is single-writer focused and an embedded library, but it's a sophisticated database engine after all, so comparisons with other "real databases" are more than appropriate. This meme really needs to die. Even more so when all you're comparing is query plan debugging output where there is no justification for unreadable output.