Reorder docs on lexical structure slightly for clarity.

Thom Brown
This commit is contained in:
Robert Haas 2010-08-13 01:12:51 +00:00
parent ed3ea3fa0c
commit 5be77ca563

View File

@ -1,4 +1,4 @@
<!-- $PostgreSQL: pgsql/doc/src/sgml/syntax.sgml,v 1.147.2.4 2010/08/12 02:04:07 momjian Exp $ --> <!-- $PostgreSQL: pgsql/doc/src/sgml/syntax.sgml,v 1.147.2.5 2010/08/13 01:12:51 rhaas Exp $ -->
<chapter id="sql-syntax"> <chapter id="sql-syntax">
<title>SQL Syntax</title> <title>SQL Syntax</title>
@ -47,12 +47,6 @@
special character is adjacent to some other token type). special character is adjacent to some other token type).
</para> </para>
<para>
Additionally, <firstterm>comments</firstterm> can occur in SQL
input. They are not tokens, they are effectively equivalent to
whitespace.
</para>
<para> <para>
For example, the following is (syntactically) valid SQL input: For example, the following is (syntactically) valid SQL input:
<programlisting> <programlisting>
@ -65,6 +59,12 @@ INSERT INTO MY_TABLE VALUES (3, 'hi there');
commands can usefully be split across lines). commands can usefully be split across lines).
</para> </para>
<para>
Additionally, <firstterm>comments</firstterm> can occur in SQL
input. They are not tokens, they are effectively equivalent to
whitespace.
</para>
<para> <para>
The SQL syntax is not very consistent regarding what tokens The SQL syntax is not very consistent regarding what tokens
identify commands and which are operands or parameters. The first identify commands and which are operands or parameters. The first