Back out syntax case changes --- seems they were intentional.

This commit is contained in:
Bruce Momjian 2010-08-12 02:03:58 +00:00
parent 568e709372
commit 47eeb5e662

View File

@ -1,4 +1,4 @@
<!-- $PostgreSQL: pgsql/doc/src/sgml/syntax.sgml,v 1.151 2010/08/11 21:48:51 momjian Exp $ --> <!-- $PostgreSQL: pgsql/doc/src/sgml/syntax.sgml,v 1.152 2010/08/12 02:03:58 momjian Exp $ -->
<chapter id="sql-syntax"> <chapter id="sql-syntax">
<title>SQL Syntax</title> <title>SQL Syntax</title>
@ -56,9 +56,9 @@
<para> <para>
For example, the following is (syntactically) valid SQL input: For example, the following is (syntactically) valid SQL input:
<programlisting> <programlisting>
SELECT * FROM my_table; SELECT * FROM MY_TABLE;
UPDATE my_table SET a = 5; UPDATE MY_TABLE SET A = 5;
INSERT INTO my_table VALUES (3, 'hi there'); INSERT INTO MY_TABLE VALUES (3, 'hi there');
</programlisting> </programlisting>
This is a sequence of three commands, one per line (although this This is a sequence of three commands, one per line (although this
is not required; more than one command can be on a line, and is not required; more than one command can be on a line, and
@ -146,11 +146,11 @@ INSERT INTO my_table VALUES (3, 'hi there');
</indexterm> </indexterm>
Key words and unquoted identifiers are case insensitive. Therefore: Key words and unquoted identifiers are case insensitive. Therefore:
<programlisting> <programlisting>
UPDATE my_table SET a = 5; UPDATE MY_TABLE SET A = 5;
</programlisting> </programlisting>
can equivalently be written as: can equivalently be written as:
<programlisting> <programlisting>
UPDATE my_table SET a = 5; uPDaTE my_TabLE SeT a = 5;
</programlisting> </programlisting>
A convention often used is to write key words in upper A convention often used is to write key words in upper
case and names in lower case, e.g.: case and names in lower case, e.g.: