summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTom Lane2005-11-04 02:56:31 +0000
committerTom Lane2005-11-04 02:56:31 +0000
commitc6843f7726a0a90b8a1ed86f6525f96c067c76b9 (patch)
tree96bbed3e83ade292c13bc39f53e2e71640f1bb02
parent6577e2017c4d1f7a4eabc6d557f00ab07f07c5dd (diff)
Avoid referring to a specific version of the SQL standard except where
necessary, and be careful to refer to the right version where it is useful to do so. This partially reverts an ill-considered search and replace from a few months ago.
-rw-r--r--doc/src/sgml/array.sgml2
-rw-r--r--doc/src/sgml/ddl.sgml8
-rw-r--r--doc/src/sgml/ecpg.sgml4
-rw-r--r--doc/src/sgml/errcodes.sgml2
-rw-r--r--doc/src/sgml/func.sgml5
-rw-r--r--doc/src/sgml/intro.sgml2
6 files changed, 12 insertions, 11 deletions
diff --git a/doc/src/sgml/array.sgml b/doc/src/sgml/array.sgml
index 8c8fe1bf0d..e9c30fdc11 100644
--- a/doc/src/sgml/array.sgml
+++ b/doc/src/sgml/array.sgml
@@ -63,7 +63,7 @@ CREATE TABLE tictactoe (
</para>
<para>
- An alternative syntax, which conforms to the SQL:2003 standard, may
+ An alternative syntax, which conforms to the SQL standard, may
be used for one-dimensional arrays.
<structfield>pay_by_quarter</structfield> could have been defined
as:
diff --git a/doc/src/sgml/ddl.sgml b/doc/src/sgml/ddl.sgml
index 7c3d6449e5..7a34ffe274 100644
--- a/doc/src/sgml/ddl.sgml
+++ b/doc/src/sgml/ddl.sgml
@@ -1058,8 +1058,8 @@ CREATE TABLE order_items (
<para>
<productname>PostgreSQL</productname> implements table inheritance
- which can be a useful tool for database designers. The SQL:2003
- standard optionally defines type inheritance which differs in many
+ which can be a useful tool for database designers. SQL:1999 and
+ later define a type inheritance feature, which differs in many
respects from the features described here.
</para>
@@ -1323,7 +1323,7 @@ WHERE c.altitude &gt; 500 and c.tableoid = p.oid;
<para>
In previous versions of <productname>PostgreSQL</productname>, the
default behavior was not to include child tables in queries. This was
- found to be error prone and is also in violation of the SQL:2003
+ found to be error prone and is also in violation of the SQL
standard. Under the old syntax, to get the sub-tables you append
<literal>*</literal> to the table name. For example:
<programlisting>
@@ -1364,7 +1364,7 @@ SELECT * from cities*;
<para>
Currently, partitioning is implemented in conjunction with table
- inheritance only, though using fully SQL:2003 compliant syntax.
+ inheritance only, though using fully SQL compliant syntax.
Table inheritance allows tables to be split into partitions, and
constraint exclusion allows partitions to be selectively combined
as needed to satisfy a particular <command>SELECT</command>
diff --git a/doc/src/sgml/ecpg.sgml b/doc/src/sgml/ecpg.sgml
index 09dbd6bd76..502baee2b4 100644
--- a/doc/src/sgml/ecpg.sgml
+++ b/doc/src/sgml/ecpg.sgml
@@ -1145,8 +1145,8 @@ struct
<para>
The fields <literal>sqlca.sqlstate</literal> and
<literal>sqlca.sqlcode</literal> are two different schemes that
- provide error codes. Both are specified in the SQL standard, but
- <literal>SQLCODE</literal> has been marked deprecated in SQL-92
+ provide error codes. Both are derived from the SQL standard, but
+ <literal>SQLCODE</literal> has been marked deprecated in the SQL-92
edition of the standard and has been dropped in later editions.
Therefore, new applications are strongly encouraged to use
<literal>SQLSTATE</literal>.
diff --git a/doc/src/sgml/errcodes.sgml b/doc/src/sgml/errcodes.sgml
index bcfc6e3726..75d5be59ec 100644
--- a/doc/src/sgml/errcodes.sgml
+++ b/doc/src/sgml/errcodes.sgml
@@ -127,7 +127,7 @@
<row>
<entry>Class 02</entry>
-<entry>No Data &mdash; this is also a warning class per SQL:2003</entry>
+<entry>No Data &mdash; this is also a warning class per the SQL standard</entry>
</row>
<row>
diff --git a/doc/src/sgml/func.sgml b/doc/src/sgml/func.sgml
index 09b7b6ed84..763852f1e6 100644
--- a/doc/src/sgml/func.sgml
+++ b/doc/src/sgml/func.sgml
@@ -2675,8 +2675,9 @@ cast(-44 as bit(12)) <lineannotation>111111010100</lineannotation>
There are three separate approaches to pattern matching provided
by <productname>PostgreSQL</productname>: the traditional
<acronym>SQL</acronym> <function>LIKE</function> operator, the
- more recent <function>SIMILAR TO</function> operator (part of
- SQL:2003), and <acronym>POSIX</acronym>-style regular expressions.
+ more recent <function>SIMILAR TO</function> operator (added in
+ SQL:1999), and <acronym>POSIX</acronym>-style regular
+ expressions.
Additionally, a pattern matching function,
<function>substring</function>, is available, using either
<function>SIMILAR TO</function>-style or POSIX-style regular
diff --git a/doc/src/sgml/intro.sgml b/doc/src/sgml/intro.sgml
index 530ecc1fdd..6fd5571cd6 100644
--- a/doc/src/sgml/intro.sgml
+++ b/doc/src/sgml/intro.sgml
@@ -98,7 +98,7 @@ $PostgreSQL$
<para>
<productname>PostgreSQL</productname> is an open-source descendant
- of this original Berkeley code. It supports a large part of the SQL:2003
+ of this original Berkeley code. It supports a large part of the SQL
standard and offers many modern features:
<itemizedlist spacing="compact">