From: | Paul Förster <paul(dot)foerster(at)gmail(dot)com> |
---|---|
To: | "Markhof, Ingolf" <ingolf(dot)markhof(at)de(dot)verizon(dot)com> |
Cc: | Cybertec Schönig & Schönig GmbH <laurenz(dot)albe(at)cybertec(dot)at>, Adam Brusselback <adambrusselback(at)gmail(dot)com>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, raf <raf(at)raf(dot)org>, "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: How to keep format of views source code as entered? |
Date: | 2021-01-26 13:51:39 |
Message-ID: | BCC054EB-27C3-48C3-B86C-1F997CEF054D@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi Ingolf,
> On 26. Jan, 2021, at 14:41, Markhof, Ingolf <ingolf(dot)markhof(at)de(dot)verizon(dot)com> wrote:
>
> You may not be able to delete tables / views that are referenced by other users objects, e.g. views. Unless you add the CASCADE option which will cause all depending views to be deleted as well. And the CASCASE will work and delete the other users view even when you don't have the permission to drop that other users view!
>
> Looks like the Oracle concept of marking views as invalid makes some sense...
yes, PostgreSQL's and Oracle's approaches IMHO both make perfect sense in their own way, depending on your design philosophy. I never said otherwise. I just said that I hate to debug invalid objects in Oracle because Oracle does not clearly show dependencies and reading source code can be hard, especially if the author was one of those genius generators which produce tons of code.
Cheers,
Paul
From | Date | Subject | |
---|---|---|---|
Next Message | Stacey Haysler | 2021-01-26 20:31:20 | Re: Code of Conduct plan,Re: Code of Conduct plan,Re: Code of Conduct plan,Re: Code of Conduct plan |
Previous Message | Markhof, Ingolf | 2021-01-26 13:41:50 | Re: How to keep format of views source code as entered? |