aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>2010-08-12 02:03:58 +0000
committerBruce Momjian <bruce@momjian.us>2010-08-12 02:03:58 +0000
commit47eeb5e662735a9c4a70b7ad7bd33944ece26a98 (patch)
treeeaca0b9e5388f2e0793e6f51c313421b7024d543
parent568e709372abad30075c299be28956b5922219b4 (diff)
downloadpostgresql-47eeb5e662735a9c4a70b7ad7bd33944ece26a98.tar.gz
postgresql-47eeb5e662735a9c4a70b7ad7bd33944ece26a98.zip
Back out syntax case changes --- seems they were intentional.
-rw-r--r--doc/src/sgml/syntax.sgml12
1 files changed, 6 insertions, 6 deletions
diff --git a/doc/src/sgml/syntax.sgml b/doc/src/sgml/syntax.sgml
index d2d14dbe9fc..4ae3df325c9 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.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">
<title>SQL Syntax</title>
@@ -56,9 +56,9 @@
<para>
For example, the following is (syntactically) valid SQL input:
<programlisting>
-SELECT * FROM my_table;
-UPDATE my_table SET a = 5;
-INSERT INTO my_table VALUES (3, 'hi there');
+SELECT * FROM MY_TABLE;
+UPDATE MY_TABLE SET A = 5;
+INSERT INTO MY_TABLE VALUES (3, 'hi there');
</programlisting>
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
@@ -146,11 +146,11 @@ INSERT INTO my_table VALUES (3, 'hi there');
</indexterm>
Key words and unquoted identifiers are case insensitive. Therefore:
<programlisting>
-UPDATE my_table SET a = 5;
+UPDATE MY_TABLE SET A = 5;
</programlisting>
can equivalently be written as:
<programlisting>
-UPDATE my_table SET a = 5;
+uPDaTE my_TabLE SeT a = 5;
</programlisting>
A convention often used is to write key words in upper
case and names in lower case, e.g.: