It just occurred to me that a correctly working fsync() could very well fix the file length caching problem without this patch.
Please hold off on applying this patch until the original test case is run with a working fsync(). Thanks. > I've found the cause of the sqlite3 database corruption in NestedVM. > The current NestedVM sys_fstat() implementation caches the old file > length() in certain circumstances. This can cause a lot of trouble > for SQLite database integrity, as you can imagine. > > The attached patch avoids file length caching in fstat() (in JDK 1.4.2) > and allows the test case to successfully run to completion and > produce a database file with the correct md5sum. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "SQLiteJDBC" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups-beta.google.com/group/sqlitejdbc?hl=en -~----------~----~----~----~------~----~------~--~---
