From: Bruce Momjian <bruce@momjian.us>
Date: Tue, 22 Feb 2011 01:14:02 +0000 (-0500)
Subject: Move information_schema duplicate constraint note to the top of the
X-Git-Tag: REL9_1_ALPHA4~119
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=fee7802770669398359c369aee83277dcc58edd1;p=postgresql

Move information_schema duplicate constraint note to the top of the
information schema documentation because it affects several tables.
---

diff --git a/doc/src/sgml/information_schema.sgml b/doc/src/sgml/information_schema.sgml
index 91c2dd4d52..32e9083744 100644
--- a/doc/src/sgml/information_schema.sgml
+++ b/doc/src/sgml/information_schema.sgml
@@ -21,6 +21,19 @@
   <productname>PostgreSQL</productname>-specific views.
  </para>
 
+ <note>
+  <para>
+   The SQL standard requires constraint names to be unique within a
+   schema;  <productname>PostgreSQL</productname>, however, does not
+   enforce this restriction.  If duplicate-named constraints are
+   stored in the same <productname>PostgreSQL</productname> schema,
+   a standard-compliant query that expects to return one matching
+   constraint row might return several, one row for each matching
+   constraint stored in the specified schema. 
+  </para>
+ </note>
+
+
  <sect1 id="infoschema-schema">
   <title>The Schema</title>
 
@@ -3212,18 +3225,6 @@ ORDER BY c.ordinal_position;
    </tgroup>
   </table>
 
-  <note>
-   <para>
-    The SQL standard requires constraint names to be unique within a
-    schema;  <productname>PostgreSQL</productname>, however, does not
-    enforce this restriction.  If duplicate-named constraints are
-    stored in the same <productname>PostgreSQL</productname> schema, a
-    standard-compliant query that expects to return one row might
-    return several, one for each matching constraint stored in the
-    specified schema.
-   </para>
-  </note>
-
  </sect1>
 
  <sect1 id="infoschema-role-column-grants">