From: | Bernd Helmle <mailings(at)oopsware(dot)de> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: WIP: Automatic view update rules |
Date: | 2009-01-19 08:18:09 |
Message-ID: | D0E54F0A0C463C23FE9383CF@teje |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
--On Samstag, Januar 17, 2009 02:01:15 +0200 Peter Eisentraut
<peter_e(at)gmx(dot)net> wrote:
> * It is not clear how automatic rules and manual DO ALSO rules should
> interact. A manual DO ALSO rule will currently clear out an automatic
> INSTEAD rule, which I find to be illogical.
My intentional feeling was that it would be a bad idea to leave any
implicit rule when someone is going to create his own rule set on a view,
at least to avoid any confusion or side effects. Consider someone having
his own rules upgrading from an older version. He must have at least his
own DO INSTEAD Rule, it doesn't make any sense to have his own DO ALSO Rule
without an INSTEAD one. Thus, doing it this way will leave the view as
expected from the original setup.
*thinking more*...if we teach explicit DO ALSO rules *not* to clean out
implicit ones, we will have the following workflows:
a) View is updatable, has its own automatic DO INSTEAD rule: if someone is
restoring his old update rules, he will have at least his own DO INSTEAD
rule. This will drop any corresponding automatically created rule, adding
his own DO INSTEAD rule and any DO ALSO rule.
b) View is updatable, has its own automatic DO INSTEAD rule: The user is
able to create any additional DO ALSO rule.
I don't see any problems here, as long as the implicit DO INSTEAD rule gets
replaced.
Opinions?
--
Thanks
Bernd
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2009-01-19 09:23:12 | Re: libpq WSACleanup is not needed |
Previous Message | Heikki Linnakangas | 2009-01-19 07:16:00 | Re: Hot Standby dev build (v8) |