Commit 9b0a8686 authored by Robert Haas's avatar Robert Haas

Reorder docs on lexical structure slightly for clarity.

Thom Brown
parent 30c22eb8
<!-- $PostgreSQL: pgsql/doc/src/sgml/syntax.sgml,v 1.152 2010/08/12 02:03:58 momjian Exp $ --> <!-- $PostgreSQL: pgsql/doc/src/sgml/syntax.sgml,v 1.153 2010/08/13 01:12:38 rhaas Exp $ -->
<chapter id="sql-syntax"> <chapter id="sql-syntax">
<title>SQL Syntax</title> <title>SQL Syntax</title>
...@@ -47,12 +47,6 @@ ...@@ -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'); ...@@ -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
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment