Sorry, I should clarify, I meant the chances of the database corruption. You are right, in a properly designed system the access to the database would take into account a changed password, which would be the normal scenario. But, if there is even a small possibility that a database would be "corrupted" because of an extraneous connection (regardless of how well the system is designed), then it could be a problem. The database being unreadable due to a wrong password is good because it is functioning the right way like you stated. It shouldn't however become corrupt. Again, I am quite sure it is simply something that I am doing wrong on my end so I need to revisit all the codepaths for this procedure in my code. Thanks!
> From: slav...@bigfraud.org > Date: Mon, 24 Oct 2011 04:45:24 +0100 > To: sqlite-users@sqlite.org > Subject: Re: [sqlite] ChangePassword method problem > > > On 24 Oct 2011, at 4:42am, Farhan Husain wrote: > > > So, I was just wondering how you would deal with multiple processes > > accessing the database. You can't guarantee that all would be closing the > > connection properly. It would seem that if all connections needed to be > > closed before a proper changepassword call can take place, then the chances > > of database corruption would increase in a multi-process/multi-access > > environment. > > How did you expect it to work when you designed the system ? After all, > changing the password to a database when lots of other processes are reading > it would naturally cause problems for those processes. They would all > suddenly start generating errors because they'd be unable to access their > data. > > Simon. > _______________________________________________ > 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
