|
1 | | -<!-- $PostgreSQL: pgsql/doc/src/sgml/syntax.sgml,v 1.150 2010/08/05 18:21:17 tgl Exp $ --> |
| 1 | +<!-- $PostgreSQL: pgsql/doc/src/sgml/syntax.sgml,v 1.151 2010/08/1121:48:51 momjian Exp $ --> |
2 | 2 |
|
3 | 3 | <chapter id="sql-syntax"> |
4 | 4 | <title>SQL Syntax</title> |
|
56 | 56 | <para> |
57 | 57 | For example, the following is (syntactically) valid SQL input: |
58 | 58 | <programlisting> |
59 | | -SELECT * FROMMY_TABLE; |
60 | | -UPDATEMY_TABLE SETA = 5; |
61 | | -INSERT INTOMY_TABLE VALUES (3, 'hi there'); |
| 59 | +SELECT * FROMmy_table; |
| 60 | +UPDATEmy_table SETa = 5; |
| 61 | +INSERT INTOmy_table VALUES (3, 'hi there'); |
62 | 62 | </programlisting> |
63 | 63 | This is a sequence of three commands, one per line (although this |
64 | 64 | 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'); |
146 | 146 | </indexterm> |
147 | 147 | Key words and unquoted identifiers are case insensitive. Therefore: |
148 | 148 | <programlisting> |
149 | | -UPDATEMY_TABLE SETA = 5; |
| 149 | +UPDATEmy_table SETa = 5; |
150 | 150 | </programlisting> |
151 | 151 | can equivalently be written as: |
152 | 152 | <programlisting> |
153 | | -uPDaTE my_TabLE SeT a = 5; |
| 153 | +UPDATE my_table SET a = 5; |
154 | 154 | </programlisting> |
155 | 155 | A convention often used is to write key words in upper |
156 | 156 | case and names in lower case, e.g.: |
|