Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Minor improvement to FAQ #22. |
|---|---|
| Downloads: | Tarball | ZIP archive | SQL archive |
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA1: |
2b950c2ead909d43da8d7d32c1493692 |
| User & Date: | mistachkin 2013-07-17 07:21:42 |
Context
|
2013-07-17
| ||
| 08:25 | Add another vtable test. check-in: 430fef73ed user: mistachkin tags: trunk | |
| 07:21 | Minor improvement to FAQ #22. check-in: 2b950c2ead user: mistachkin tags: trunk | |
|
2013-07-16
| ||
| 19:48 | Prevent native database connection handles from entering the connection pool if they have been used to create a virtual table module. check-in: 7b49ab3bf0 user: mistachkin tags: trunk | |
Changes
Changes to www/faq.wiki.
538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 |
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> |
| | | | |
538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 |
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, SQLiteStatement, 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> |