| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | Vik Fearing <vik(at)2ndquadrant(dot)fr>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, denisa(dot)cirstescu(at)asentinel(dot)com, "pgsql-docs(at)postgresql(dot)org" <pgsql-docs(at)postgresql(dot)org> |
| Subject: | Re: Undocumented behavior od DROP SCHEMA ... CASCADE |
| Date: | 2016-08-12 20:32:11 |
| Message-ID: | 13204.1471033931@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
I wrote:
> If we're going to add a warning about CASCADE being recursive, it would
> logically need to be added to every last DROP command that has a CASCADE
> option, which is most of them. I don't necessarily object to that, but
> we'd need a more boiler-plate, copy-and-pasteable phrasing.
> ...
> I'm inclined to suggest that maybe the generic phrasing could be
> "Automatically drop objects that depend on the <whatever> [(such as ...)],
> and in turn all objects that depend on those objects".
Not hearing any alternative suggestions, I'm going to go do something
like the above.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2016-08-12 20:55:08 | Re: Undocumented behavior od DROP SCHEMA ... CASCADE |
| Previous Message | Simon Riggs | 2016-08-12 17:59:16 | Re: Wording in TABLESAMPLE documentation |