mirror of
https://git.postgresql.org/git/postgresql.git
synced 2025-03-01 19:45:33 +08:00
Move information_schema duplicate constraint note to the top of the
information schema documentation because it affects several tables.
This commit is contained in:
parent
ede45e90dd
commit
fee7802770
@ -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">
|
||||
|
Loading…
Reference in New Issue
Block a user