Rod Taylor wrote:
> > David Kaplan reminded me that there is another UI issue to be
> > considered: when we *are* doing a DROP CASCADE, should the dropped
> > dependent objects be reported somehow? As it stands, Rod's patch emits
> > elog(NOTICE) messages in this case, but I am wondering whether that will
> > be seen as useful or merely annoying chatter.
>
> If the notices about implicit drops (triggers on tables, etc.) has been
> found to be useful in both creation and destruction then I would assume
> that this information would be wanted as well.
>
> If the above information has not been found to be useful in the past,
> then I would expect it to continue as chatter.
>
> Personally, I find it to be chatter and turn off NOTICES in general, but
> believe it to be consistent with similar messages in the past.
Agreed. If you issue a single DROP that hits other objects, I think
people would want to see that, but then again, if you drop the table,
you would expect triggers and sequences to disappear with no mention.
Tough one.
-- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610)
853-3000+ If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill,
Pennsylvania19026
