-C Catch\san\sout-of-memory\scondition\sin\svacuum\scode.\s(Bug\sin\s(3373)).\s(CVS\s3675)
-D 2007-03-06T16:03:56
+C Change\sthe\sdocumentation\sto\sbe\smore\sspecific\sabout\sthe\srestriction\son\nthe\suse\sof\skeywords.\s\sTicket\s#2264.\s(CVS\s3676)
+D 2007-03-08T12:23:34
F Makefile.in 1fe3d0b46e40fd684e1e61f8e8056cefed16de9f
F Makefile.linux-gcc 2d8574d1ba75f129aba2019f0b959db380a90935
F README 9c4e2d6706bdcc3efdd773ce752a8cdab4f90028
F www/index-ex1-x-b.gif f9b1d85c3fa2435cf38b15970c7e3aa1edae23a3
F www/index.tcl 688cf1280232f4964d8d07fda65e166a4b2e16cc
F www/indirect1b1.gif adfca361d2df59e34f9c5cac52a670c2bfc303a1
-F www/lang.tcl 5e7888c2d33ff521173ece39ddad53596700e2d9
+F www/lang.tcl f76b1853bf5ac5677f9381c4ce9ab0c3c2519b26
F www/lockingv3.tcl f59b19d6c8920a931f096699d6faaf61c05db55f
F www/mingw.tcl d96b451568c5d28545fefe0c80bee3431c73f69c
F www/nulls.tcl ec35193f92485b87b90a994a01d0171b58823fcf
F www/vdbe.tcl 87a31ace769f20d3627a64fa1fade7fed47b90d0
F www/version3.tcl 890248cf7b70e60c383b0e84d77d5132b3ead42b
F www/whentouse.tcl 97e2b5cd296f7d8057e11f44427dea8a4c2db513
-P d6986d1e7cba1d114fa06c5560ffc6bb1feb7389
-R c16e20d8f67a08a215ee8c71d404c60c
-U danielk1977
-Z 12839403eb12ec38912c51a8e61dab13
+P 302ec768579e2f7c17a33749e685289a041aeb11
+R 7749edec062d6de6cf82b3267f875132
+U drh
+Z 527bcee1d1ae23e7c72be8880f2bc02b
#
# Run this Tcl script to generate the lang-*.html files.
#
-set rcsid {$Id: lang.tcl,v 1.122 2007/02/13 02:03:25 drh Exp $}
+set rcsid {$Id: lang.tcl,v 1.123 2007/03/08 12:23:34 drh Exp $}
source common.tcl
if {[llength $argv]>0} {
#
set keyword_list [lsort {
ABORT*
+ ADD
AFTER*
ALL
ALTER
+ ANALYZE*
AND
AS
ASC*
BY
CASCADE*
CASE
+ CAST*
CHECK
COLLATE
COMMIT
GLOB*
GROUP
HAVING
+ IF*
IGNORE*
IMMEDIATE*
IN
OR
ORDER
OUTER
+ PLAN*
PRAGMA*
PRIMARY
+ QUERY*
RAISE*
REFERENCES
REINDEX*
VACUUM*
VALUES
VIEW*
+ VIRTUAL*
WHEN
WHERE
}]
puts {
<p>The SQL standard specifies a huge number of keywords which may not
-be used as the names of tables, indices, columns, or databases. The
-list is so long that few people can remember them all. For most SQL
-code, your safest bet is to never use any English language word as the
-name of a user-defined object.</p>
+be used as the names of tables, indices, columns, databases, user-defined
+functions, collations, virtual table modules, or any other named object.
+The list of keywords is so long that few people can remember them all.
+For most SQL code, your safest bet is to never use any English language
+word as the name of a user-defined object.</p>
<p>If you want to use a keyword as a name, you need to quote it. There
are three ways of quoting keywords in SQLite:</p>
<p>Quoted keywords are unaesthetic.
To help you avoid them, SQLite allows many keywords to be used unquoted
-as the names of databases, tables, indices, triggers, views, and/or columns.
+as the names of databases, tables, indices, triggers, views, columns,
+user-defined functions, collations, attached databases, and virtual
+function modules.
In the list of keywords that follows, those that can be used as identifiers
are shown in an italic font. Keywords that must be quoted in order to be
used as identifiers are shown in bold.</p>
<p>
SQLite adds new keywords from time to time when it take on new features.
-So to prevent you code from being broken by future enhancements, you should
+So to prevent your code from being broken by future enhancements, you should
normally quote any indentifier that is an English language word, even if
you do not have to.
</p>