System.Data.SQLite

Check-in [ef62d192d4]
Login

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

Overview
Comment:Update several wiki pages.
Downloads: Tarball | ZIP archive
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA1: ef62d192d43853917baa6919476901d253d25afb
User & Date: mistachkin 2013-06-22 03:36:42.343
Context
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
2013-05-30
00:44
Add DateTimeFormatString connection string property to allow the DateTime format string used for all parsing and formatting to be overridden. Disable use of the new connection string parsing algorithm when the No_SQLiteConnectionNewParser environment variable is set. Pursuant to [bbdda6eae2]. check-in: 4f933521a1 user: mistachkin tags: trunk
Changes
Unified Diff Ignore Whitespace Patch
Changes to www/contribute.wiki.
︙︙
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63



64
65
66
67
68
69
70


Contributors are asked to make all non-trivial changes on a branch.  A
System.Data.SQLite admin will review the branch and merge the changes
into the trunk.</p>

Contributors are required to following the
[./checkin.wiki | pre-checkin checklist] prior to every checkin to
the System.Data.SQLite self-hosting repository.  This checklist is short and succinct
and should only require a few seconds to follow.  Contributors
should print out a copy of the pre-checkin checklist and keep
it on a notecard beside their workstations, for quick reference.

Contributors should review and try to mimic the coding style
used through the rest of the System.Data.SQLite source code.  Your code should
blend in.  A third-party reader should be unable to distinguish your
code from any other code in the source corpus.




<h2>4.0 Testing</h2>

System.Data.SQLite has several automated test suites that excercise its base
functionality, but this is an area that needs further work.
(Your contributions here are welcomed!)
Contributors with check-in privileges are expected to run the test suites








|
|







>
>
>








48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73


Contributors are asked to make all non-trivial changes on a branch.  A
System.Data.SQLite admin will review the branch and merge the changes
into the trunk.</p>

Contributors are required to following the
[./checkin.wiki | pre-checkin checklist] prior to every checkin to
the System.Data.SQLite self-hosting repository.  This checklist is short and
succinct and should only require a few seconds to follow.  Contributors
should print out a copy of the pre-checkin checklist and keep
it on a notecard beside their workstations, for quick reference.

Contributors should review and try to mimic the coding style
used through the rest of the System.Data.SQLite source code.  Your code should
blend in.  A third-party reader should be unable to distinguish your
code from any other code in the source corpus.

Furthermore, all new code must contain &quot;documentation comments&quot; that
can be successfully processed up by the Microsoft C# compiler.

<h2>4.0 Testing</h2>

System.Data.SQLite has several automated test suites that excercise its base
functionality, but this is an area that needs further work.
(Your contributions here are welcomed!)
Contributors with check-in privileges are expected to run the test suites
︙︙
Changes to www/faq.wiki.
︙︙
106
107
108
109
110
111
112







113
114
115
116
117
118
119

  </li>
  <br>
  <li>
    <a href="#q21">Is this behavior a bug? <b>-OR-</b> Is there a quick way to
    view the various lists of tickets for the System.Data.SQLite project?
    </a>
  </li>







</ol>

<hr>
<a name="q1"></a>
<p>
  <b>(1) When will the next version of System.Data.SQLite be released?</b>
</p>








>
>
>
>
>
>
>








106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126

  </li>
  <br>
  <li>
    <a href="#q21">Is this behavior a bug? <b>-OR-</b> Is there a quick way to
    view the various lists of tickets for the System.Data.SQLite project?
    </a>
  </li>
  <br>
  <li>
    <a href="#q22">Since upgrading a project to use System.Data.SQLite version
    1.0.82.0 (or later), the database file is <b>still locked</b> after all its
    connections have been closed.  Why is this happening?
    </a>
  </li>
</ol>

<hr>
<a name="q1"></a>
<p>
  <b>(1) When will the next version of System.Data.SQLite be released?</b>
</p>
︙︙
518
519
520
521
522
523
524



















      The list of tickets fixed and then closed.
    </a></li>
    <li><a href="/index.html/rptview?rn=7">
      The list of tickets closed without needing a fix.
    </a></li>
  </ol>
</p>


























>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>

525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549

      The list of tickets fixed and then closed.
    </a></li>
    <li><a href="/index.html/rptview?rn=7">
      The list of tickets closed without needing a fix.
    </a></li>
  </ol>
</p>

<hr>
<a name="q22"></a>
<p>
  <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>