database/postgres
database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-05-01 01:04:50 +03:00
Code

Move information_schema duplicate constraint note to the top of the

Browse Source 
information schema documentation because it affects several tables.
This commit is contained in:
Bruce Momjian 2011-02-21 20:14:02 -05:00
parent ede45e90dd
commit fee7802770
1 changed files with 13 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

25
doc/src/sgml/information_schema.sgml
View File

@ -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;
</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">