Not supposed to be the contents....just attributes... Also note the 15-second default time window. If you do it faster than 15 seconds you won't see the effect.
http://support.microsoft.com/kb/172190 http://dfstream.blogspot.com/2012/02/file-system-tunneling-in-windows.html Not sure if Windows 7 has it too but I would imagine so. Can you turn it off and see what happens? Michael D. Black Senior Scientist Advanced Analytics Directorate Advanced GEOINT Solutions Operating Unit Northrop Grumman Information Systems ________________________________ From: sqlite-users-boun...@sqlite.org [sqlite-users-boun...@sqlite.org] on behalf of Joel Lucsy [jjlu...@gmail.com] Sent: Friday, June 29, 2012 10:50 AM To: i...@psunrise.com; General Discussion of SQLite Database Subject: EXT :Re: [sqlite] An interesting (strange) issue with selects There is a "bug" that I've read about on a Windows machines sporting the NTFS filesystem that when a file is deleted and recreated within a certain period of time, the original file is retrieved rather than a new one. On Fri, Jun 29, 2012 at 10:54 AM, Dennis Volodomanov <i...@psunrise.com>wrote: > On 30/06/2012 12:19 AM, Black, Michael (IS) wrote: > >> >> It persists across a reboot? >> >> You can create a database, delete it, reboot, and your app will still see >> the original table? >> >> All I can say is wow...your system is really hosed. >> >> Even anti-virus shouldn't cause that. This would infer some sort of >> caching that is semi-permanent. >> >> Have you got a 2nd computer you can test this on? >> >> Would you be willing to share your app so others can check this? As >> "House" used to say..."interesting". >> >> >> > Not only my app, the sqlite shell will see it too. Regarding my second > message - I was talking about this same screwed-up folder, so yes, I can > create a new db in a new folder and it's fine. It's only when I try > anything in this folder that things go amok (at least it's localized to > this folder so far). > > I'll do testing on another machine and I'll do a full chkdsk here as well > tomorrow. > > Most likely - it is my box that's causing this. Unless SQLite does any > sort of real low-level disk access, bypassing standard OS, then it's > unlikely that it somehow caused this to happen, but it would be good to > rule this out somehow. > > I can share the app (not the source of course), sure, but I don't know if > that'll help in any way? > > > Dennis > > ______________________________**_________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-**bin/mailman/listinfo/sqlite-**users<http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users<http://sqlite.org:8080/cgi-**bin/mailman/listinfo/sqlite-**users%3Chttp://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users>> > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
