Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Change the documentation to be more specific about the restriction on the use of keywords. Ticket #2264. (CVS 3676) |
|---|---|
| Downloads: | Tarball | ZIP archive |
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA1: |
d03d480544e1f782ca796e4cfb83ff68 |
| User & Date: | drh 2007-03-08 12:23:34.000 |
Context
|
2007-03-09
| ||
| 14:40 | Add a few "class" attributes to the html generated by lang.tcl to support conversion to pdf. (CVS 3677) (check-in: 485c52ddc0 user: danielk1977 tags: trunk) | |
|
2007-03-08
| ||
| 12:23 | Change the documentation to be more specific about the restriction on the use of keywords. Ticket #2264. (CVS 3676) (check-in: d03d480544 user: drh tags: trunk) | |
|
2007-03-06
| ||
| 16:03 | Catch an out-of-memory condition in vacuum code. (Bug in (3373)). (CVS 3675) (check-in: 302ec76857 user: danielk1977 tags: trunk) | |
Changes
Changes to www/lang.tcl.
1 2 3 | # # Run this Tcl script to generate the lang-*.html files. # | | | 1 2 3 4 5 6 7 8 9 10 11 |
#
# Run this Tcl script to generate the lang-*.html files.
#
set rcsid {$Id: lang.tcl,v 1.123 2007/03/08 12:23:34 drh Exp $}
source common.tcl
if {[llength $argv]>0} {
set outputdir [lindex $argv 0]
} else {
set outputdir ""
}
|
| ︙ | ︙ | |||
1861 1862 1863 1864 1865 1866 1867 1868 1869 1870 1871 1872 1873 1874 1875 1876 1877 1878 1879 1880 1881 1882 1883 1884 1885 1886 1887 1888 |
}
# A list of keywords. A asterisk occurs after the keyword if it is on
# the fallback list.
#
set keyword_list [lsort {
ABORT*
AFTER*
ALL
ALTER
AND
AS
ASC*
ATTACH*
AUTOINCREMENT
BEFORE*
BEGIN*
BETWEEN
BY
CASCADE*
CASE
CHECK
COLLATE
COMMIT
CONFLICT*
CONSTRAINT
CREATE
CROSS
| > > > | 1861 1862 1863 1864 1865 1866 1867 1868 1869 1870 1871 1872 1873 1874 1875 1876 1877 1878 1879 1880 1881 1882 1883 1884 1885 1886 1887 1888 1889 1890 1891 |
}
# A list of keywords. A asterisk occurs after the keyword if it is on
# the fallback list.
#
set keyword_list [lsort {
ABORT*
ADD
AFTER*
ALL
ALTER
ANALYZE*
AND
AS
ASC*
ATTACH*
AUTOINCREMENT
BEFORE*
BEGIN*
BETWEEN
BY
CASCADE*
CASE
CAST*
CHECK
COLLATE
COMMIT
CONFLICT*
CONSTRAINT
CREATE
CROSS
|
| ︙ | ︙ | |||
1909 1910 1911 1912 1913 1914 1915 1916 1917 1918 1919 1920 1921 1922 | FOR* FOREIGN FROM FULL GLOB* GROUP HAVING IGNORE* IMMEDIATE* IN INDEX INITIALLY* INNER INSERT | > | 1912 1913 1914 1915 1916 1917 1918 1919 1920 1921 1922 1923 1924 1925 1926 | FOR* FOREIGN FROM FULL GLOB* GROUP HAVING IF* IGNORE* IMMEDIATE* IN INDEX INITIALLY* INNER INSERT |
| ︙ | ︙ | |||
1937 1938 1939 1940 1941 1942 1943 1944 1945 1946 1947 1948 1949 1950 1951 1952 | NULL OF* OFFSET* ON OR ORDER OUTER PRAGMA* PRIMARY RAISE* REFERENCES REINDEX* RENAME* REPLACE* RESTRICT* RIGHT | > > | 1941 1942 1943 1944 1945 1946 1947 1948 1949 1950 1951 1952 1953 1954 1955 1956 1957 1958 | NULL OF* OFFSET* ON OR ORDER OUTER PLAN* PRAGMA* PRIMARY QUERY* RAISE* REFERENCES REINDEX* RENAME* REPLACE* RESTRICT* RIGHT |
| ︙ | ︙ | |||
1965 1966 1967 1968 1969 1970 1971 1972 1973 1974 1975 1976 1977 1978 1979 1980 1981 |
UNION
UNIQUE
UPDATE
USING
VACUUM*
VALUES
VIEW*
WHEN
WHERE
}]
Section {SQLite keywords} keywords
puts {
<p>The SQL standard specifies a huge number of keywords which may not
| > | > | | | | 1971 1972 1973 1974 1975 1976 1977 1978 1979 1980 1981 1982 1983 1984 1985 1986 1987 1988 1989 1990 1991 1992 1993 1994 1995 1996 1997 1998 1999 2000 |
UNION
UNIQUE
UPDATE
USING
VACUUM*
VALUES
VIEW*
VIRTUAL*
WHEN
WHERE
}]
Section {SQLite keywords} keywords
puts {
<p>The SQL standard specifies a huge number of keywords which may not
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>
<blockquote>
<table>
|
| ︙ | ︙ | |||
2005 2006 2007 2008 2009 2010 2011 |
compatibility.</td></tr>
</table>
</blockquote>
</p>
<p>Quoted keywords are unaesthetic.
To help you avoid them, SQLite allows many keywords to be used unquoted
| | > > | | 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 2025 2026 2027 2028 2029 2030 2031 2032 2033 2034 2035 2036 |
compatibility.</td></tr>
</table>
</blockquote>
</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, 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 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>
<p>
The following are the keywords currently recognized by SQLite:
</p>
|
| ︙ | ︙ |