Re: When to use SQLite3 [was Re: 'Lite' Databases (Re: sqlite3 and dates)]

2015-02-18 Thread Ethan Furman
On 02/18/2015 08:59 PM, Steve Hayes wrote: > I would summarise it by saying [...] if you want a standalone database on > a single machine, use SQLite. It sounds like SQLite would also work fine if that single-machine scenario was a web-app with not-too-many users trying to write at once. -- ~E

Re: When to use SQLite3 [was Re: 'Lite' Databases (Re: sqlite3 and dates)]

2015-02-18 Thread Steve Hayes
On Wed, 18 Feb 2015 20:15:30 -0800, Ethan Furman wrote: >At the risk of using actual data, I looked this up at >http://www.sqlite.org/whentouse.html: > > >Checklist For Choosing The Right Database Engine Interesting. A couple of months ago I asked in comp.databases what the differences were b

When to use SQLite3 [was Re: 'Lite' Databases (Re: sqlite3 and dates)]

2015-02-18 Thread Ethan Furman
At the risk of using actual data, I looked this up at http://www.sqlite.org/whentouse.html: Checklist For Choosing The Right Database Engine * Is the data separated from the application by a network? → choose client/server Relational database engines act as a bandwidth-reducing data filt