On 03/07/12 18:53, Keith Edmunds wrote:
We've used SQLite for a lightweight database. There are some restrictions, but I suspect it will work well in your situation.
I've never actually used SQLite, despite having the intention of doing so on several occasions. Part of the reason[*] is that we have quite an extensive library of database code that is abstracted to a small degree (I did at one point have it working on PostgreSQL, although that was some time ago and it's not been used or maintained that way for a few years now) but has never been adapted for SQLite, so there'd be quite a bit of work.
How similar is the SQL syntax between SQLite and MySQL? I know it's lightweight in terms of overheads but what is it like for data throughput compared with MySQL? To be honest I would quite like this to be excuse to port our libraries to SQLite if I can justify it.
[*] The biggest reason this never happens is that most of our applications in the past have run on hosted web servers running more than one application, which means MySQL is likely already there and in use, so adding an extra DB server is always an extra memory overhead. Now that we're doing more single-purpose systems on ARM boards that argument has finally run out of steam!