Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit9b0a868

Browse files
committed
Reorder docs on lexical structure slightly for clarity.
Thom Brown
1 parent30c22eb commit9b0a868

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

‎doc/src/sgml/syntax.sgml

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
<!-- $PostgreSQL: pgsql/doc/src/sgml/syntax.sgml,v 1.152 2010/08/12 02:03:58 momjian Exp $ -->
1+
<!-- $PostgreSQL: pgsql/doc/src/sgml/syntax.sgml,v 1.153 2010/08/13 01:12:38 rhaas Exp $ -->
22

33
<chapter id="sql-syntax">
44
<title>SQL Syntax</title>
@@ -47,12 +47,6 @@
4747
special character is adjacent to some other token type).
4848
</para>
4949

50-
<para>
51-
Additionally, <firstterm>comments</firstterm> can occur in SQL
52-
input. They are not tokens, they are effectively equivalent to
53-
whitespace.
54-
</para>
55-
5650
<para>
5751
For example, the following is (syntactically) valid SQL input:
5852
<programlisting>
@@ -65,6 +59,12 @@ INSERT INTO MY_TABLE VALUES (3, 'hi there');
6559
commands can usefully be split across lines).
6660
</para>
6761

62+
<para>
63+
Additionally, <firstterm>comments</firstterm> can occur in SQL
64+
input. They are not tokens, they are effectively equivalent to
65+
whitespace.
66+
</para>
67+
6868
<para>
6969
The SQL syntax is not very consistent regarding what tokens
7070
identify commands and which are operands or parameters. The first

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp