That MSDN article only applies to 'System Restore'. System Restore does not do anything with "User Data" but only with "System Data". Of course, if you store "User Data" in a place where "System Data" is supposed to be stored, then your "User Data" is "System Data", not "User Data", and subject to management by Windows Automagic, oftentimes contrary to your desires or explicit instructions to the contrary (since you are no longer the manager of the data).
For "User Data" stored in "User Data" locations, System Restore does nothing. The most likely cause of the issue is that the application is storing data in a "System Managed" location, such as "Program Files", "Program Files (x86)" or anywhere under "Windows", "WinNT", or whatever directory is pointed to by %SystemRoot%, rather than in a user data directory. If this is the case, and specific modifications to the application and the permissions where the application is trying to write the data, then the magical "Virtualization" mis-feature will be redirecting "some" operations to an alternate location, and you have to look in that other location to ensure the file is gone. This "Application Virtualization" is a mis-feature because it only half works half of the time. Most of the time it creates more problems than it solves. Unfortunately like most mis-features in Windows, there is no "Off" switch. You simply have to learn to live with its brokenness-by-design and once bitten, don't do that anymore. >-----Original Message----- >From: [email protected] [mailto:sqlite-users- >[email protected]] On Behalf Of Simon Slavin >Sent: Sunday, 19 October, 2014 17:58 >To: General Discussion of SQLite Database >Subject: Re: [sqlite] Data error > > >On 18 Oct 2014, at 6:25am, aaquib Khan <[email protected]> wrote: > >> i have encountered a strange issue lately, i am using sqllite in my >windows >> application. The logic in application is, at the start of the >application >> db file is created, and it is deleted when the application is closed. >Now >> when i again start my application the db file is created but it >contains >> old data which was deleted successfully > >Do you know it was deleted successfully ? Are you checking the results >returned from the DELETE, the _finalize(), and the _close() ? > >> i even tried to manually >> shift+delete the db file but in vain, the old data comes back somehow, >any >> solution for this to not happen. > >Windows does some broken caching of some files and ignores what has >actually happened on disk: > ><http://msdn.microsoft.com/en- >us/library/windows/desktop/aa378870(v=vs.85).aspx> > >Pick an unusual file extension nobody else has ever thought of, and try >that. See if that fixes the problem. > >Simon. >_______________________________________________ >sqlite-users mailing list >[email protected] >http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
