From 5be77ca563e8dce4fbaa15387186de8448a7a413 Mon Sep 17 00:00:00 2001 From: Robert Haas <rhaas@postgresql.org> Date: Fri, 13 Aug 2010 01:12:51 +0000 Subject: [PATCH] Reorder docs on lexical structure slightly for clarity. Thom Brown --- doc/src/sgml/syntax.sgml | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/doc/src/sgml/syntax.sgml b/doc/src/sgml/syntax.sgml index 96817c05cf..3d108e1e46 100644 --- a/doc/src/sgml/syntax.sgml +++ b/doc/src/sgml/syntax.sgml @@ -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"> <title>SQL Syntax</title> @@ -47,12 +47,6 @@ special character is adjacent to some other token type). </para> - <para> - Additionally, <firstterm>comments</firstterm> can occur in SQL - input. They are not tokens, they are effectively equivalent to - whitespace. - </para> - <para> For example, the following is (syntactically) valid SQL input: <programlisting> @@ -65,6 +59,12 @@ INSERT INTO MY_TABLE VALUES (3, 'hi there'); commands can usefully be split across lines). </para> + <para> + Additionally, <firstterm>comments</firstterm> can occur in SQL + input. They are not tokens, they are effectively equivalent to + whitespace. + </para> + <para> The SQL syntax is not very consistent regarding what tokens identify commands and which are operands or parameters. The first -- 2.49.0