Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
Comment: | Change some (English language) grammar in faq.tcl. Ticket #2480. No code changes. (CVS 4195) |
---|---|
Downloads: | Tarball | ZIP archive |
Timelines: | family | ancestors | descendants | both | trunk |
Files: | files | file ages | folders |
SHA1: |
e526817f158883f617720fd389741a29 |
User & Date: | danielk1977 2007-08-03 08:18:45.000 |
Context
2007-08-05
| ||
23:52 | Fix some compiler warnings. (CVS 4196) (check-in: 6cc15409ad user: drh tags: trunk) | |
2007-08-03
| ||
08:18 | Change some (English language) grammar in faq.tcl. Ticket #2480. No code changes. (CVS 4195) (check-in: e526817f15 user: danielk1977 tags: trunk) | |
07:33 | Avoid reloading the schema when an expired statement is finalized or reset. This is only necessary when the in-memory schema does not match the file-system schema. (CVS 4194) (check-in: 61de5b52da user: danielk1977 tags: trunk) | |
Changes
Changes to www/faq.tcl.
1 2 3 | # # Run this script to generated a faq.html output file # | | | 1 2 3 4 5 6 7 8 9 10 11 | # # Run this script to generated a faq.html output file # set rcsid {$Id: faq.tcl,v 1.39 2007/08/03 08:18:45 danielk1977 Exp $} source common.tcl header {SQLite Frequently Asked Questions</title>} set cnt 1 proc faq {question answer} { set ::faq($::cnt) [list [string trim $question] [string trim $answer]] incr ::cnt |
︙ | ︙ | |||
198 199 200 201 202 203 204 | <p>If you turn on <a href="capi3ref.html#sqlite3_enable_shared_cache">shared cache</a> mode or if you compile with the -DSQLITE_ENABLE_MEMORY_MANAGEMENT=1 option, then you can never move an <b>sqlite3</b> pointer across threads. The <b>sqlite3</b> pointer must only be used in the same thread in which it was created by <a href="capi3ref.html#sqlite3_open">sqlite3_open()</a>. If you | | | | | 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 | <p>If you turn on <a href="capi3ref.html#sqlite3_enable_shared_cache">shared cache</a> mode or if you compile with the -DSQLITE_ENABLE_MEMORY_MANAGEMENT=1 option, then you can never move an <b>sqlite3</b> pointer across threads. The <b>sqlite3</b> pointer must only be used in the same thread in which it was created by <a href="capi3ref.html#sqlite3_open">sqlite3_open()</a>. If you break the rules and use an <b>sqlite3</b> handle in more than one thread under these circumstances you will likely corrupt some internal data structures, resulting in a crash.</p> <p>Under UNIX, you should not carry an open SQLite database across a fork() system call into the child process. Problems will result if you do.</p> } faq { |
︙ | ︙ |