-C Fix\sa\sbug\sin\sout-of-memory\sprocessing\sintroduced\sby\scheck-in\s(3336).\s(CVS\s3346)
-D 2006-08-12T13:28:23
+C Documentation\schanges\sprior\sto\sthe\srelease\sof\s3.3.7.\s(CVS\s3347)
+D 2006-08-12T14:38:47
F Makefile.in 9c2a76055c305868cc5f5b73e29a252ff3632c0a
F Makefile.linux-gcc 2d8574d1ba75f129aba2019f0b959db380a90935
F README 9c4e2d6706bdcc3efdd773ce752a8cdab4f90028
-F VERSION 301ed2b2c08f5cca242ea56e50a9ed0264a3eb76
+F VERSION ef6abd4b2095b0f378b428ed251e16f0213fcf3f
F aclocal.m4 a8df0ae21d1ac797fa7d7eaa1703412bc61b973f
F addopcodes.awk 701697fae48376375ec8532c3d04e910cfeef352
F art/2005osaward.gif 0d1851b2a7c1c9d0ccce545f3e14bca42d7fd248
F www/autoinc.tcl b357f5ba954b046ee35392ce0f884a2fcfcdea06
F www/c_interface.tcl b51b08591554c16a0c3ef718364a508ac25abc7e
F www/capi3.tcl 7a7cc225fe02eb7ab861a6019b08baa0014409e1
-F www/capi3ref.tcl de1db9415d6ac5908cad436ce4598eba8f536c4a
-F www/changes.tcl ec6d4fa4d302a76d662509c7c4796a159bd66b31
+F www/capi3ref.tcl fab3d77e72fcea574e0fd52e6374d75143792f1c
+F www/changes.tcl 7bbcf947aa71d4760cbd286ba176466e729c974f
F www/common.tcl 14d121c28532ad20c3e349caa4db708b0b822083
F www/compile.tcl 276546d7eb445add5a867193bbd80f6919a6b084
F www/conflict.tcl cdd0f4b59b0ba6d61f67e6a38f3ae45853bacb30
F www/dynload.tcl 02eb8273aa78cfa9070dd4501dca937fb22b466c
F www/faq.tcl 705c986e40775cc3d92a1676dcbb55f00f0459c5
F www/fileformat.tcl 900c95b9633abc3dcfc384d9ddd8eb4876793059
-F www/formatchng.tcl c9f5ded025504b4ae6a39cb8a6630709a981f6b5
+F www/formatchng.tcl bbb8af1ee494a71031acac4c8d8c51535f23b9df
F www/fullscanb.gif f7c94cb227f060511f8909e10f570157263e9a25
F www/index-ex1-x-b.gif f9b1d85c3fa2435cf38b15970c7e3aa1edae23a3
-F www/index.tcl 17cdd87e0b5e5eff158309f5209b86e47f964604
+F www/index.tcl 7b9c5747a838501dace958131755651d6ca31adb
F www/indirect1b1.gif adfca361d2df59e34f9c5cac52a670c2bfc303a1
F www/lang.tcl d5414bd9f63ea3763887893b437d0dce4ad4f403
F www/lockingv3.tcl f59b19d6c8920a931f096699d6faaf61c05db55f
F www/mingw.tcl d96b451568c5d28545fefe0c80bee3431c73f69c
F www/nulls.tcl ec35193f92485b87b90a994a01d0171b58823fcf
-F www/oldnews.tcl f0491f4f69ec114ecd168077f2df48022b1352b2
+F www/oldnews.tcl 788051b8be60ea94730c36a712a3a8257fe6696e
F www/omitted.tcl ee6b46f83d513b2187869740da829a700e1a355e
F www/opcode.tcl 5bd68059416b223515a680d410a9f7cb6736485f
F www/optimizer.tcl d6812a10269bd0d7c488987aac0ad5036cace9dc
F www/vdbe.tcl 87a31ace769f20d3627a64fa1fade7fed47b90d0
F www/version3.tcl 890248cf7b70e60c383b0e84d77d5132b3ead42b
F www/whentouse.tcl 97e2b5cd296f7d8057e11f44427dea8a4c2db513
-P 0f667c4abd73bbb806a5efb31b0aba6efaf40fb8
-R a8c31200fcc8f48468c75930300e9f9d
+P 8d98a205cbe9948039884947db33f41a63a09062
+R 020f98eb0b5ebf9cf9f7532c7acdc3ce
U drh
-Z 4b532ece7981c40705cd0ee53d51dac0
+Z 58bf8fd026ffb0a54c491cc992142204
-8d98a205cbe9948039884947db33f41a63a09062
\ No newline at end of file
+c276cca2aafc1b417e12ba7119c65902ef7d61ec
\ No newline at end of file
-set rcsid {$Id: capi3ref.tcl,v 1.41 2006/06/26 21:35:46 drh Exp $}
+set rcsid {$Id: capi3ref.tcl,v 1.42 2006/08/12 14:38:47 drh Exp $}
source common.tcl
header {C/C++ Interface For SQLite Version 3}
puts {
same aggregate instance) the same buffer is returned. The implementation
of the aggregate can use the returned buffer to accumulate data.
- The buffer allocated is freed automatically by SQLite.
+ The buffer is freed automatically by SQLite when the query that
+ invoked the aggregate function terminates.
}
api {} {
#define SQLITE_TRANSIENT ((void(*)(void *))-1)
} {
In the SQL strings input to sqlite3_prepare() and sqlite3_prepare16(),
- one or more literals can be replace by a parameter "?" or ":AAA" or "\$VVV"
+ one or more literals can be replace by a parameter "?" or ":AAA" or
+ "@AAA" or "\$VVV"
where AAA is an alphanumeric identifier and VVV is a variable name according
to the syntax rules of the TCL programming language.
The values of these parameters (also called "host parameter names")
special value SQLITE_STATIC, then the library assumes that the information
is in static, unmanaged space and does not need to be freed. If the
fifth argument has the value SQLITE_TRANSIENT, then SQLite makes its
- own private copy of the data before returning.
+ own private copy of the data immediately, before the sqlite3_bind_*()
+ routine returns.
The sqlite3_bind_*() routines must be called after
sqlite3_prepare() or sqlite3_reset() and before sqlite3_step().
const char *sqlite3_bind_parameter_name(sqlite3_stmt*, int n);
} {
Return the name of the n-th parameter in the precompiled statement.
- Parameters of the form ":AAA" or "\$VVV" have a name which is the
- string ":AAA" or "\$VVV". In other words, the initial ":" or "$"
+ Parameters of the form ":AAA" or "@AAA" or "\$VVV" have a name which is the
+ string ":AAA" or "\$VVV". In other words, the initial ":" or "$" or "@"
is included as part of the name.
Parameters of the form "?" have no name.
+ The first bound parameter has an index of 1, not 0.
+
If the value n is out of range or if the n-th parameter is nameless,
then NULL is returned. The returned string is always in the
UTF-8 encoding.
database. Closing the database from a busy handler will delete
data structures out from under the executing query and will
probably result in a coredump.
+
+ There can only be a single busy handler defined for each database
+ connection. Setting a new busy handler clears any previous one.
+ Note that calling sqlite3_busy_timeout() will also set or clear
+ the busy handler.
}
api {} {
Calling this routine with an argument less than or equal to zero
turns off all busy handlers.
+
+ There can only be a single busy handler for a particular database
+ connection. If another busy handler was defined
+ (using sqlite3_busy_handler()) prior to calling
+ this routine, that other busy handler is cleared.
}
api {} {
one or more complete SQL statements.
The argument must be a nul-terminated UTF-8 string for sqlite3_complete()
and a nul-terminated UTF-16 string for sqlite3_complete16().
+
+ These routines do not check to see if the SQL statement is well-formed.
+ They only check to see that the statement is terminated by a semicolon
+ that is not part of a string literal and is not inside
+ the body of a trigger.
} {}
api {} {
puts "<DD><P><UL>$desc</UL></P></DD>"
}
+chng {2006 August 12 (3.3.7)} {
+<li>Added support for
+<a href="http://www.sqlite.org/cvstrac/wiki?p=VirtualTables">virtual tables</a>
+(beta)</li>
+<li>Added support for
+<a href="http://www.sqlite.org/cvstrac/wiki?p=LoadableExtensions">
+dynamically loaded extensions</a> (beta)</li>
+<li>The
+<a href="capi3ref.html#sqlite3_interrupt">sqlite3_interrupt()</a>
+routine can be called for a different thread</li>
+<li>Added the <a href="lang_expr.html#match">MATCH</a> operator.</li>
+<li>The default file format is now 1.
+}
+
chng {2006 June 6 (3.3.6)} {
<li>Plays better with virus scanners on windows</li>
<li>Faster :memory: databases</li>
#
# Run this Tcl script to generate the formatchng.html file.
#
-set rcsid {$Id: formatchng.tcl,v 1.18 2006/06/27 12:24:14 drh Exp $ }
+set rcsid {$Id: formatchng.tcl,v 1.19 2006/08/12 14:38:47 drh Exp $ }
source common.tcl
header {File Format Changes in SQLite}
puts {
edition.</p>
</td>
</tr>
+<tr>
+ <td valign="top">3.3.6 to 3.3.7</td>
+ <td valign="top">2006-Aug-12</td>
+ <td><p>The previous file format change has caused so much
+ grief that the default behavior has been changed back to
+ the original file format. This means that DESC option on
+ indices is ignored by default that the more efficient encoding
+ of boolean values is not used. In that way, older versions
+ of SQLite can read and write databases created by newer
+ versions. If the new features are desired, they can be
+ enabled using pragma: "PRAGMA legacy_file_format=OFF".</p>
+ <p>To be clear: both old and new file formats continue to
+ be understood and continue to work. But the old file format
+ is used by default instead of the new. This might change
+ again in some future release - we may go back to generating
+ the new file format by default - but probably not until
+ all users have upgraded to a version of SQLite that will
+ understand the new file format. That might take several
+ years.</p></td>
+</tr>
</table>
</blockquote>
puts "<hr width=\"50%\">"
}
+newsitem {2006-Aug-12} {Version 3.3.7} {
+ Version 3.3.7 includes support for loadable extensions and virtual
+ tables. But both features are still considered "beta" and their
+ APIs are subject to change in a future release. This release is
+ mostly to make available the minor bug fixes that have accumulated
+ since 3.3.6. Upgrading is not necessary. Do so only if you encounter
+ one of the obscure bugs that have been fixed or if you want to try
+ out the new features.
+}
+
newsitem {2006-Jun-19} {New Book About SQLite} {
<a href="http://www.apress.com/book/bookDisplay.html?bID=10130">
<i>The Definitive Guide to SQLite</i></a>, a new book by
Upgrade only if you are having problems or need one of the new features.
}
-newsitem {2006-Feb-11} {Version 3.3.4} {
- This release fixes several bugs, including a
- a blunder that might cause a deadlock on multithreaded systems.
- Anyone using SQLite in a multithreaded environment should probably upgrade.
-}
-
-newsitem {2006-Jan-31} {Version 3.3.3 stable} {
- There have been no major problems discovered in version 3.3.2, so
- we hereby declare the new APIs and language features to be stable
- and supported.
-}
-
puts {
<p align="right"><a href="oldnews.html">Old news...</a></p>
</td></tr></table>
}
-footer {$Id: index.tcl,v 1.141 2006/07/02 10:21:36 drh Exp $}
+footer {$Id: index.tcl,v 1.142 2006/08/12 14:38:47 drh Exp $}
}
+newsitem {2006-Feb-11} {Version 3.3.4} {
+ This release fixes several bugs, including a
+ a blunder that might cause a deadlock on multithreaded systems.
+ Anyone using SQLite in a multithreaded environment should probably upgrade.
+}
+
+newsitem {2006-Jan-31} {Version 3.3.3 stable} {
+ There have been no major problems discovered in version 3.3.2, so
+ we hereby declare the new APIs and language features to be stable
+ and supported.
+}
+
newsitem {2006-Jan-24} {Version 3.3.2 beta} {
More bug fixes and performance improvements as we move closer to
a production-ready version 3.3.x.
Plans are to continue to support SQLite version 2.8 with
bug fixes. But all new development will occur in version 3.0.
}
-footer {$Id: oldnews.tcl,v 1.15 2006/06/27 11:14:13 drh Exp $}
+footer {$Id: oldnews.tcl,v 1.16 2006/08/12 14:38:47 drh Exp $}
projects / thirdparty / sqlite.git / commitdiff
