On 12 Apr 2010, at 11:47am, Navaneeth Sen B wrote: > Hi Simon, >> These two are not problems, depending on how 'simultaneous' you want to be >> (milliseconds ?). SQLite handles multi-user locking if your CE platform and >> operating system does. By the way, I don't know what 'CE' means. > > Does that mean it does not support this kind of concurrency? > Can you please explain how SQLite handles multi-user locking? > I have read somewhere in the SQLite site that it does not support High > concurrency, like when you are reading a part of the database, you cant > write to the other part of the DB.
SQLite does not lock at the record level. When you commit a change to the database the entire database is locked for a short time. But it is a very short time. If you are only reading or writing 3000 records at a time, and you have appropriate indexes, then this is unlikely to be a problem for you. But you should probably test an SQLite solution to get an idea how long these updates and queries will take for your platform. And thanks for your explanation of 'CE'. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
