On Fri, 15 Sep 2006 17:29:13 -0400, you wrote: Hi Liam
>I have a database that has one writer which runs once a day, and >potentially many readers running whenever someone wants some >information. I am trying to understand concurrency in sqlite3 so that I do a daily Job too in my programm. It seems to me, there are likewise rules. If you allow reading while another Process do a big writing, several reader possible get different results, while writer is not ready. Thats not a Sqlite-Problem, its the same to all other DB. The better way is, to lock the Table while it is be written and allow reading then, if this Jobs is ready. I don't mean a read-write-dialog-process in this case , but a big writer, ideally a especially and exclusive writer. Reading isn't a primary concurrency problem, much more writing is. I do my big writing while the system is generally locked to possible 1500 users. It's customized to a time, when Users are not present - at 03:00 o'clock in the morning. >I understand from lang_transaction that if the writer starts with >BEGIN IMMEDIATE >and ends with >END >then it will be possible for readers to read the database while the >writer is updating it: Is it ok to you, that user possibly get different or premature Query-Results? Best Regards Thomas www.thlu.de ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
