Create account

raddi.net
replied 1592d
Go with SQLite, it's awesome. Unless you heavily rely on query optimizer/planner magic then there's nothing faster for local storage. I'm using SQLite for all the various things the
replied 1591d
Thanks - would you recommend replacing MySQL for SQLite on the website side of things too?
raddi.net
replied 1591d
That really depends on workload and SQL features you use. For web software which is accessed by many users at the same time I'd probably stay with MySQL. I think SQLite still has
raddi.net
replied 1591d
per-table locking only.
raddi.net
replied 1592d
client app needs to store, but network data are basically 4 tables (and 2 of them being kind-of indices), so I went ahead and again wrote custom fast storage with very little
raddi.net
replied 1592d
overhead.