Michael Russell wrote: > > 1) The break seems to have happened between 1.0.81.0 and 1.0.82.0. >
There was a change in System.Data.SQLite disposal behavior in that timeframe, namely using the new sqlite3_close_v2() API; however, everything [now] conforms to the IDisposable interface semantics and established best practices for native resource cleanup. The root issue here is that all disposable managed objects (in this case CriticalHandle derived classes) must be properly disposed by whatever uses them. Failing to do so with System.Data.SQLite used to be a source of potential access violations, etc; now, it just keeps the database connection handle active until everything has been properly disposed. > > 2) Do Entity Framework team members read this list? > I don't know. -- Joe Mistachkin _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
