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. I haven't adjusted the code based on your reply yet, but as soon as I do I will post the results. Thanks!
> From: sql...@mistachkin.com > To: sqlite-users@sqlite.org > Date: Sat, 22 Oct 2011 23:33:05 -0700 > Subject: Re: [sqlite] ChangePassword method problem > > > Farhan Husain wrote: > > > > Aah, ok. So, for all the methods that act on the database I should > explicitly add > > conn.Close() within the using conn scope? > > > > Well, I'm not familiar with your specific project; however, that does not > sound like > a bad idea. > > -- > Joe Mistachkin > > _______________________________________________ > 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
