database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-08-31 17:02:12 +03:00
Code Activity

Doc: clarify that DROP ... CASCADE is recursive.

Browse Source 
Apparently that's not obvious to everybody, so let's belabor the point.

In passing, document that DROP POLICY has CASCADE/RESTRICT options (which
it does, per gram.y) but they do nothing (I assume, anyway).  Also update
some long-obsolete commentary in gram.y.

Discussion: <20160805104837.1412.84915@wrigleys.postgresql.org>
This commit is contained in:
Tom Lane
2016-08-12 18:45:18 -04:00
parent 4b234fd8bf
commit 4997878193
35 changed files with 144 additions and 48 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
doc/src/sgml/ref/drop_transform.sgml
View File

@@ -18,7 +18,7 @@
<refsynopsisdiv>
<synopsis>
DROP TRANSFORM [ IF EXISTS ] FOR <replaceable>type_name</replaceable> LANGUAGE <replaceable>lang_name</replaceable>
DROP TRANSFORM [ IF EXISTS ] FOR <replaceable>type_name</replaceable> LANGUAGE <replaceable>lang_name</replaceable> [ CASCADE | RESTRICT ]
</synopsis>
</refsynopsisdiv>
@@ -74,7 +74,9 @@ DROP TRANSFORM [ IF EXISTS ] FOR <replaceable>type_name</replaceable> LANGUAGE <
<term><literal>CASCADE</literal></term>
<listitem>
<para>
Automatically drop objects that depend on the transform.
Automatically drop objects that depend on the transform,
and in turn all objects that depend on those objects
(see <xref linkend="ddl-depend">).
</para>
</listitem>
</varlistentry>