3 ms·
Yeah, results are what matters. SQLite's process seems to produce solid bug-free results. My only complaint would be that there's many SQL features I want to u
by hmry 9mo ago
Yeah, results are what matters. SQLite's process seems to produce solid bug-free results.
My only complaint would be that there's many SQL features I want to use which aren't supported. Surely some part of that is deliberately restricted scope, but some might also be dev velocity issues.
DuckDB (C++) can be used like an SQLite with more SQL features, but it's also a lot buggier. Segfaults from your database are not what you want.
So still hoping for some alternative to come along (or maybe I'll need to write it myself)
- chasil 9mo agoWhat isn't supported? After window functions were added, what else is missing?
- hmry 9mo agoThe ones that come to mind immediately are more ALTER statements (especially adding non-virtual columns), DATE, TIME, and TIMESTAMP types and their associated functions, and ARRAY types. Although I don't wish to disparage SQLite, they do support a lot of features. Just that I constantly run into the ones they don't, with my use cases. And beyond standard SQL, stuff like hashmap/bloom filter/vector indices, nearest neighbor search, etc...