8 ms·
I used SQLite until I found a query that locked it up seemingly forever. It had 2 inner joins. It worked with 1 inner join - NOT 2. The author of SQLite said "N
by zandorg 16y ago
I used SQLite until I found a query that locked it up seemingly forever. It had 2 inner joins. It worked with 1 inner join - NOT 2. The author of SQLite said "Not my problem buddy, it's yours". So I'm switching to PostGRE (which CAN handle those 2 inner joins) or a Microsoft SQL.
- forinti 16y agoPostgresql and MS SQL aren't really alternatives to SQLite. Maybe you just had the wrong tool to begin with.
- silentbicycle 16y agoThat's a query optimizer complexity trade-off. SQLite is targeted for embedded usage, and a smarter query optimizer would make SQLite much larger, cutting into one of its main strengths. You're better off using SQLite as a scaled-down RDBMS and moving to postgres when necessary. Lua's design makes similar trade-offs, and they comment on this in http://www.lua.org/doc/sblp2005.pdf http://www.lua.org/doc/sblp2005.pdf: "For instance, just the control-flow analysis of Bigloo, an optimizer Scheme compiler, is more than ten times larger than the whole Lua implementation." It's the same reason the core language doesn't have regular expressions. (Well, that, and LPEG.)