-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 09/12/13 10:30, Felipe Farinon wrote: > I'm sorry to repost, but I just want to confirm that there is no > interest in fixing this, so that I can handle this with a workaround in > my application.
Note that the effect will be to make SQLite slower since it would need extra system calls at various points to do metadata updates. The most accurate would be to update the timestamp on every write! Looking at the last modified date is also not the most effective way of detecting things. You can use the filesystem archive flag to detect changes since you last looked at the file. You can use a trigger internally at the SQL level to track changes in a meaningful way too. Finally you can disable the use of memory mapping - have a look at the Windows VFS. Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.14 (GNU/Linux) iEYEARECAAYFAlKmLooACgkQmOOfHg372QQ5YQCfSSIJHA7cWQQ9X1IpHGkgQnr+ K3AAn0w1Wl1OIfNhR5n0zDCMHDlIqyqD =GUnl -----END PGP SIGNATURE----- _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
