On Sun, Jan 25, 2009 at 1:07 PM, Bernd Helmle <mailings@oopsware.de> wrote:
> I didn't find such a notion in the standard. A view is automatically
> updatable if it meets the criteria of updatability). If you don't want your
> view writable, you have to GRANT the necessary ACLs.
Perhaps I'm a bit old school on this one but I don't see the point of
creating a bunch of rules on every view I create, even if I don't
especially want them to be updatable (and I think it's a very common
use case - especially because we're used to it).
Yes, I can remove them but I don't see the point of going through
every view to remove the rules.
Especially, creating these rules on upgrade seems really weird as
there is no chance the application is using updatable views: they
didn't exist in prior versions and if the application is using it, the
view already has its own set of rules for that.
> I originally had the idea of a GUC which controls wether automatic rules
> will be generated or not. But I abonded this idea, since this has some kind
> of "parametrized SQL standard functionality".
I'm more for some syntactical sugar which allows to create view with
the "updatable" property and remove this property from the view.
I don't know if it's possible though and it's just MVHO on this subject.
--
Guillaume
