Skip to content
Snippets Groups Projects
Commit fee78027 authored by Bruce Momjian's avatar Bruce Momjian
Browse files

Move information_schema duplicate constraint note to the top of the

information schema documentation because it affects several tables.
parent ede45e90
No related branches found
No related tags found
No related merge requests found
...@@ -21,6 +21,19 @@ ...@@ -21,6 +21,19 @@
<productname>PostgreSQL</productname>-specific views. <productname>PostgreSQL</productname>-specific views.
</para> </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"> <sect1 id="infoschema-schema">
<title>The Schema</title> <title>The Schema</title>
...@@ -3212,18 +3225,6 @@ ORDER BY c.ordinal_position; ...@@ -3212,18 +3225,6 @@ ORDER BY c.ordinal_position;
</tgroup> </tgroup>
</table> </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>
<sect1 id="infoschema-role-column-grants"> <sect1 id="infoschema-role-column-grants">
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment