diff options
author | Bruce Momjian | 2011-02-22 01:14:02 +0000 |
---|---|---|
committer | Bruce Momjian | 2011-02-22 01:14:02 +0000 |
commit | fee7802770669398359c369aee83277dcc58edd1 (patch) | |
tree | f64b79e369ddb25e3d140eb54ff3bbb0049065c9 | |
parent | ede45e90dd1992bfd3e1e61ce87bad494b81f54d (diff) |
Move information_schema duplicate constraint note to the top of the
information schema documentation because it affects several tables.
-rw-r--r-- | doc/src/sgml/information_schema.sgml | 25 |
1 files changed, 13 insertions, 12 deletions
diff --git a/doc/src/sgml/information_schema.sgml b/doc/src/sgml/information_schema.sgml index 91c2dd4d525..32e90837443 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"> |