-C Version\s2.7.6\s(CVS\s850)
-D 2003-01-25T16:32:14
+C Added\ssection\son\scomments.\nCorrected\sbroken\s</p>\send\stags.\s(CVS\s851)
+D 2003-01-26T15:28:18
F Makefile.in 6606854b1512f185b8e8c779b8d7fc2750463d64
F Makefile.linux-gcc b86a99c493a5bfb402d1d9178dcdc4bd4b32f906
F README f1de682fbbd94899d50aca13d387d1b3fd3be2dd
F www/fileformat.tcl a4b5c2c6e89b7d42d09f97fd4d7bbd39cbf24936
F www/formatchng.tcl b4449e065d2da38b6563bdf12cf46cfe1d4d765e
F www/index.tcl b5265ca54a5124ec40bffb7c7943e072e074d61a
-F www/lang.tcl 1ea38a9fe867e4fed2220f519f5c0862e7022c53
+F www/lang.tcl 1c11172bd6511b39d2c69f153a5e82332d0379ef
F www/mingw.tcl f1c7c0a7f53387dd9bb4f8c7e8571b7561510ebc
F www/nulls.tcl 29497dac2bc5b437aa7e2e94577dad4d8933ed26
F www/omitted.tcl 118062f40a203fcb88b8d68ef1d7c0073ac191ec
F www/sqlite.tcl ae3dcfb077e53833b59d4fcc94d8a12c50a44098
F www/tclsqlite.tcl 1db15abeb446aad0caf0b95b8b9579720e4ea331
F www/vdbe.tcl 2013852c27a02a091d39a766bc87cff329f21218
-P b6ea0da76a27a4a67a3978c53405840518de2379
-R 4cf2a85c454063f72e76dc7b464fd72d
-U drh
-Z 7ed6fddf31ad03fda6646e399fd6e633
+P bdba796f3b89690ab5d53a9e16924383ef72657c
+R 2fbda7b77729464b96834537506192f2
+U jplyon
+Z 22282820ee286f511aad4850aeea1aad
#
# Run this Tcl script to generate the sqlite.html file.
#
-set rcsid {$Id: lang.tcl,v 1.47 2003/01/11 14:19:52 drh Exp $}
+set rcsid {$Id: lang.tcl,v 1.48 2003/01/26 15:28:18 jplyon Exp $}
puts {<html>
<head>
{DELETE delete}
{UPDATE update}
{SELECT select}
+ {comment comment}
{COPY copy}
{EXPLAIN explain}
{expression expr}
</p>
}
+
+Section comment comment
+
+Syntax {comment} {<SQL-comment> | <C-comment>
+} {SQL-comment} {-- <single-line>
+} {C-comment} {/STAR <multiple-lines> [STAR/]
+}
+
+
+puts {
+<p> Comments aren't SQL commands, but can occur in SQL queries. They are
+treated as whitespace by the parser. They can begin anywhere whitespace
+can be found, including inside expressions that span multiple lines.
+</p>
+
+<p> SQL comments only extend to the end of the current line.</p>
+
+<p> C comments can span any number of lines. If there is no terminating
+delimiter, they extend to the end of the input. This is not treated as
+an error. A new SQL statement can begin on a line after a multiline
+comment ends. C comments can be embedded anywhere whitespace can occur,
+including inside expressions, and in the middle of other SQL statements.
+C comments do not nest. SQL comments inside a C comment will be ignored.
+</p>
+}
+
+
Section COPY copy
Syntax {sql-statement} {
in PostgreSQL. In fact, the SQLite COPY command is specifically
designed to be able to read the output of the PostgreSQL dump
utility <b>pg_dump</b> so that data can be easily transferred from
-PostgreSQL into SQLite.<p>
+PostgreSQL into SQLite.</p>
<p>The table-name is the name of an existing table which is to
be filled with data. The filename is a string or identifier that
names a file from which data will be read. The filename can be
-the <b>STDIN</b> to read data from standard input.<p>
+the <b>STDIN</b> to read data from standard input.</p>
<p>Each line of the input file is converted into a single record
in the table. Columns are separated by tabs. If a tab occurs as
projects / thirdparty / sqlite.git / commitdiff
