Moving from v1.0.81.0 to v1.0.83.0 (no code changes on my part), results in a change in reported state from the SQLiteConnection.State property.
I could not find any documentation/bug fixes which indicates that this is an expected change. Background info: Vb.net app, .NET 3.5SP1, VS 2010, OS=Win 7 The database being opened is encrypted via system.data.sqlite, and the code goes through the following: 1 - check cn.state (sees it is not open) a- set connection string cn.connectionString b- try to open connection object (w/o a password) c- it, as expected, fails d- loop back, but note that we just tried without a password so try #2 will use a password 2 - start loop again with a check of cn.state -> w/ v81 this shows as not open so I know to try to open again with a password -> w/ v83 this now shows open! (i.e. - state=System.Data.ConnectionSate.Open) I can re-work my code to handle the new behavior (I expect), but I just want to be sure this is an expected change in what is returned from Connection.ConnectionState. Thanks, Denis _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
