Denis Burke wrote:
>
> 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.
>
The change causing the behavior you are seeing was made in release 1.0.82.0.
Prior to that release, opening a connection would always execute several
PRAGMA
commands against the connection prior to returning. As a side-effect of
this,
it would detect incorrect passwords right away.
However, as of release 1.0.82.0, the PRAGMA commands are only executed if
the
connection settings to be used actually differ from the defaults.
The change is here:
https://system.data.sqlite.org/index.html/ci/9dfa1577a6?sbs=0
>
> 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.
>
For your code to be robust using release 1.0.82.0 or later, you'll want to
execute a command (any command that reads the schema will work) against the
connection prior to considering the password as "correct".
--
Joe Mistachkin
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
