Andrew Moss, on Wednesday, May 8, 2019 10:42 AM, wrote... >We are currently backed into a corner by a customer and are looking at >using an SQLite database hosted on a windows network share (using server >2012 R2 or later). We are well aware this is not advisable and have read >https://www.sqlite.org/whentouse.html.
This is true, so, this is the "law." >My question is, if we limit the application (through other means) to a >single writer, but allow multiple readers, does that remove the risk of >database corruption from multiple SQLite processes? >Any notes from other users who had to do something similar in the past? What I can tell you is that we have been using a setup with 8 writers and readers and it has work since 2007. Although, you will have some timeouts, but as long as you have explained the users that when this happens, hit Save again, ;-). Your setup should work, if you only have one writer, from my experience, of course. I have set a PRAGMA busy_timeout = 5000; so allow for multiple writers to work, which gives SQLite time to save, and have the next writer wait, and within the program have a function handle this. So, for us (8 writers and readers), it has work with minimal timeout instances, and one database corruption back in 2010. But, I believe that Dr. Hipp and his team has fixed many of the problems that hindered us back then. Also, we only use 1 thread to write. I hope this helps. josé <http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users> _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
