These blog posts have been great. I'd love to see a deep dive on the query planner at some point.<p>I've done lots of benchmarking SQLite while writing ducks [1], and found some interesting stuff. It seems like SQLite will only use one index, even in cases where two indexes would better suit the query. Or, in cases where the query is fetching most of the table, it will use an index even though a full scan would actually be much faster.<p>Don't get me wrong, SQLite is awesome, and it's quite possible to work around these behaviors. Just interested in why they're not built in.<p>[1] <a href="https://github.com/manimino/ducks" rel="nofollow">https://github.com/manimino/ducks</a>
> SQL was originally designed for non-technical users to interact with the database, however, it's used almost exclusively by software developers peppering it throughout their applications.<p>Interesting claim! In my experience, the # of data analysts / BI analysts / etc that write and have mastered SQL vastly exceeds the # of web developers (especially if we focus on developers actually writing SQL instead of using ORMs)
The EXPLAIN keyword is really awesome. It also allows you to quickly validate SQLite command text without actually executing it. We have found this to be useful for real-time validation of user inputs when working on SQL-based config tools.<p>Note that EXPLAIN also seamlessly incorporates any application-defined functions, so you can validate <i>everything</i> is as expected. Useful when being clever with DSLs and such.
Most people probably don't know this but SQLite is used under the covers for most Mac OS applications like Photos and Mail. Been that way for a long time and lets you do some interesting data mining.<p>e.g. <a href="https://javarants.com/build-your-own-mail-analyzer-for-mac-mail-app-747143e94ccc" rel="nofollow">https://javarants.com/build-your-own-mail-analyzer-for-mac-m...</a>
I wonder how an alternate timeline might have played out if Richard Hipp had not named it "SQLite" and instead called it "SQLightning" or "SQLExpress" or something like that. For much of its lifetime, SQLite wasn't taken seriously despite being an extraordinary technology and part of me is convinced it was in large part due to "Lite" being in the name.
I really like this series of blog posts on SQLite, thanks if you are reading this. It was really informative for me since I did not know much about its internals before
I see so many SQLite posts these days, but which companies with a lot (>1M) concurrent users are using SQLite in a non embedded fashion?<p>It just seems so academic. I’d like to use a web service or app backed primarily by SQLite and see how it goes.
For some reason, IME, SQLite feels the hardest to use of the popular databases. I did start my own database journey with Postgre and MSSQL so I feel kind of lost with SQLite whenever I use it.
Any dates on supporting range of ports to my running sqlite/db instance on? ex) 5999-8999<p>edit: not sure why this is being downvoted? not being able to define a range of port seems like a huge oversight. the forums there are not very active so I am asking here.