提交 fee78027 编写于 作者: B Bruce Momjian

Move information_schema duplicate constraint note to the top of the

information schema documentation because it affects several tables.
上级 ede45e90
......@@ -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">
......
Markdown is supported
0% .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑!
想要评论请 注册