System.Data.SQLite
Check-in [a86c8c24d8]
Not logged in

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview
Comment:Update to the FAQ #22.
Downloads: Tarball | ZIP archive | SQL archive
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA1: a86c8c24d8b83b285a9db45859d3ed40e8544d62
User & Date: mistachkin 2013-06-22 03:56:31
Context
2013-06-25
21:50
Add all the necessary infrastructure to allow virtual tables to be implemented in managed code. Fix for [9a544991be]. check-in: 2d35b79c48 user: mistachkin tags: trunk
2013-06-24
22:50
Merge updates from trunk. check-in: d4f5e0a0ef user: mistachkin tags: virtualTables
2013-06-22
03:56
Update to the FAQ #22. check-in: a86c8c24d8 user: mistachkin tags: trunk
03:36
Update several wiki pages. check-in: ef62d192d4 user: mistachkin tags: trunk
Changes
Hide Diffs Unified Diffs Ignore Whitespace Patch

Changes to www/faq.wiki.

536
537
538
539
540
541
542
543
544
545







546
547
548
549
  <b>(22) Since upgrading a project to use System.Data.SQLite version 1.0.82.0
  (or later), the database file is still locked after all its connections have
  been closed.  Why is this happening?
</b>
</p>

<p>
  As of version 1.0.82.0, the resources associated with a SQLiteConnection are
  not fully cleaned up until all the SQLiteCommand, SQLiteDataReader, and
  SQLiteBackup objects associated with that SQLiteConnection have also been







  disposed.  This is accomplished through careful use of the
  <a href="http://www.sqlite.org/c3ref/close.html">sqlite3_close_v2()</a> core
  native library function.
</p>







|
|
|
>
>
>
>
>
>
>
|

|

536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
  <b>(22) Since upgrading a project to use System.Data.SQLite version 1.0.82.0
  (or later), the database file is still locked after all its connections have
  been closed.  Why is this happening?
</b>
</p>

<p>
  As of version 1.0.82.0, the native resources for a SQLiteConnection object,
  including any native locks on the underlying file, are not fully released
  until all SQLiteCommand, SQLiteDataReader, and SQLiteBackup objects associated
  with that SQLiteConnection object have also been disposed.  These changes were
  made to allow the SQLite native resource management to integrate better with
  the
  <a href="http://en.wikipedia.org/wiki/Garbage_collection_%28computer_science%29">garbage collection</a>
  semantics used by the
  <a href="http://en.wikipedia.org/wiki/Common_Language_Runtime">Common Language
  Runtime</a>.  Allowing native SQLite resources to be released in a
  non-deterministic order is accomplished through careful use of the
  <a href="http://www.sqlite.org/c3ref/close.html">sqlite3_close_v2()</a> core
  native library routine.
</p>