database/sqlite
1
0
Fork 0
mirror of https://github.com/sqlite/sqlite.git synced 2025-07-30 19:03:16 +03:00
Code Activity

Fix a bug in subquery generation when the subquery is a compound select.

Browse Source 
Also added new tests to cover this case. (CVS 435)

FossilOrigin-Name: aaf7fd4cef04d3d70a0444aad1b606bfc663c3e8
This commit is contained in:
drh
2002-03-23 00:31:29 +00:00
parent 545c23dc42
commit 1cc3d75f69
7 changed files with 76 additions and 21 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
www/faq.tcl
View File

@ -1,7 +1,7 @@
#
# Run this script to generated a faq.html output file
#
set rcsid {$Id: faq.tcl,v 1.8 2002/02/19 22:42:06 drh Exp $}
set rcsid {$Id: faq.tcl,v 1.9 2002/03/23 00:31:29 drh Exp $}
puts {<html>
<head>
@ -194,12 +194,11 @@ faq {
faq {
Is SQLite threadsafe?
} {
<p>Almost. In the source file named "<b>os.c</b>" there are two functions
named <b>sqliteOsEnterMutex()</b> and <b>sqliteOsLeaveMutex()</b>. In
the default distribution these functions are stubs. They do not do anything.
If you change them so that they actually implement a mutex, then SQLite
will be threadsafe. But because these routines are stubs, the default
SQLite distribution is not threadsafe.</p>
<p>Yes. Sometimes. In order to be thread-safe, SQLite must be compiled
with the THREADSAFE preprocessor macro set to 1. In the default
distribution, the windows binaries are compiled to be threadsafe but
the linux binaries are not. If you want to change this, you'll have to
recompile.</p>
<p>"Threadsafe" in the previous paragraph means that two or more threads
can run SQLite at the same time on different "<b>sqlite</b>" structures