Hi,
On 3/29/19 12:29 PM, Alvaro Herrera wrote:
On 2019-Mar-29, Jesper Pedersen wrote:
Maybe the "(" / ")" in the CASCADE description should be removed from
ref/drop_table.sgml as part of this patch.
I'm not sure what text you propose to remove?
Just the attached.
Should catalogs.sgml be updated for this case ?
I'm not adding any new dependency type, nor modifying any existing one.
Are you looking at anything that needs changing specifically?
No, I just mentioned it if it was a requirement that the precise
use-case for each dependency type were documented.
Best regards,
Jesper
diff --git a/doc/src/sgml/ref/drop_table.sgml b/doc/src/sgml/ref/drop_table.sgml
index bf8996d198..328157c849 100644
--- a/doc/src/sgml/ref/drop_table.sgml
+++ b/doc/src/sgml/ref/drop_table.sgml
@@ -41,9 +41,9 @@ DROP TABLE [ IF EXISTS ] <replaceable
class="parameter">name</replaceable> [, ..
triggers, and constraints that exist for the target table.
However, to drop a table that is referenced by a view or a foreign-key
constraint of another table, <literal>CASCADE</literal> must be
- specified. (<literal>CASCADE</literal> will remove a dependent view
entirely,
+ specified. <literal>CASCADE</literal> will remove a dependent view entirely,
but in the foreign-key case it will only remove the foreign-key
- constraint, not the other table entirely.)
+ constraint, not the other table entirely.
</para>
</refsect1>
