<story><title>Many small queries are efficient in SQLite</title><url>https://sqlite.org/np1queryprob.html</url></story><parent_chain><item><author>Laminary</author><text>If you haven&amp;#x27;t tried SQLite, please do. For years I ignored SQLite and used MySQL (it does the job) but once you see how fast SQLite is, and advantages of having a DB contained in a single file... just go play around with SQLite instead of ignoring it for years like me. It&amp;#x27;s neat.</text></item></parent_chain><comment><author>jjoonathan</author><text>Counterpoint: I over-used SQLite because it was the first database I encountered and spent waaaay longer working around its shortcomings than I eventually spent porting to postgres.&lt;p&gt;Long version: I couldn&amp;#x27;t get bulk insert performance above absolutely miserable levels. I tried tricks like deleting and recreating indices but without luck. The perf tooling wasn&amp;#x27;t there to quickly figure out where the problem was (this was 10 years ago, not sure if things have improved) so I wound up building a version of SQLite with debug symbols and profiling it with a C profiler. The problem turned out to be a default setting that made spill-to-disk very aggressive and basically guaranteed that any workflow like mine would grind along with miserable slowness and no outward indication of what to do about it. I found an email thread where someone in effectively the same situation made some constructive suggestions and got turned away on the principle that even casual users ought to just know performance knobs like this one. Yikes. I am probably munging some of the details, but it made me angry enough to learn postgres and port my code over despite having a fix for my immediate problem.</text></comment>
<story><title>Many small queries are efficient in SQLite</title><url>https://sqlite.org/np1queryprob.html</url></story><parent_chain><item><author>Laminary</author><text>If you haven&amp;#x27;t tried SQLite, please do. For years I ignored SQLite and used MySQL (it does the job) but once you see how fast SQLite is, and advantages of having a DB contained in a single file... just go play around with SQLite instead of ignoring it for years like me. It&amp;#x27;s neat.</text></item></parent_chain><comment><author>hans_castorp</author><text>I will re-consider it, once they have proper data types and data type checking.</text></comment>