On 29 Oct 2016, at 10:21pm, Yuri <[email protected]> wrote: > I think you need to have such testcase: On the table with a lot of key/value > pairs you run a set of updates and inserts. Random file operations should > fail with some low probability with various error codes, like disk full.
You would have to simulate this on a wide range of platforms. Because what each platform does under "disk full" conditions is different. The one possible enhancement to SQLite I might suggest is to add a test for "disk full" before it tries to recover from a "file not closed properly" condition. Perhaps it should try to grab an extra block of disk first. If that fails it shouldn't attempt a rescue, just immediately return "disk full". Unfortunately this isn't done at the sqlite3_open() stage because this doesn't actually access the file. Not sure how to cope with that. Simon. _______________________________________________ sqlite-users mailing list [email protected] http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
