Dear Community,

I found a bug/different behavior in your current Sqlite .NET Version 1.0.82.0:

After performing Database Actions, we used 
SQLiteConnection Close() to close the database connection.

Afterwards, I use File.ReadAllBytes() on the Database File, which lead to a 
Access Violation because the file was still opened in a different process.
When we switched back to Version 1.0.80.0,and it worked again.

It seems like the filestream is not closed, when using SqliteConnection Close().

Is there maybe a new function to perform this action, or is there some bug in 
it?

I tried this with the following Sqlite Version:

Version: 1.0.82.0
Platform: x86
.NET Version: 3.5 SP1

Greetings,
Michael Endres
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Reply via email to