yes, let me explain better..... Having a task queue that updates heavily a sqlite database while a web application needs to read it is not a good idea. Sqlite is a wonderful database and supports some syntax that others "big databases" dream about, has transactions, is flexible, multiplatform, heavily tested, supports big sets of data, has a concise api, it's portable, scales wonderfully in "read" type of operations .... but has some problems to keep up with concurrent writes. My "is safe" was pointed to the operations you described, as in "a stream of updates". sqlite is perfectly safe, although your "updates" are going to block the db and will need to be serialized (no concurrency allowed or you'll result in an update waiting for the previous one to finish)
Il giorno martedì 15 maggio 2012 19:20:27 UTC+2, Anthony ha scritto: > > 1. with every other database that is not sqlite, it's safe because how >> most relational db work, transactions make you have always a consistent set >> of results (if you use them correctly!!) > > > It's still "safe" in SQLite -- you just might get a little more blocking > than you would with other db's. If the task isn't too frequent and the load > on the app generally not too heavy, SQLite should be fine. > > Anthony >
