| From: | Jim Nasby <decibel(at)decibel(dot)org> |
|---|---|
| To: | Talha Khan <talha(dot)amjad(at)gmail(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: A problem in inheritance |
| Date: | 2007-06-22 21:10:51 |
| Message-ID: | 9500CE34-4019-40E1-9859-34243AEEC261@decibel.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Jun 20, 2007, at 12:53 PM, Talha Khan wrote:
> THE ACTUAL TEST:
>
> DROP RULE account_login_no_update ON account_login;
>
>
> UPDATE account_login set originating_source = 'xxx';
>
> Now the update should not effect the child table but it does,
> evident
> from the output of the following query:
That's because you dropped the rule that would have affected that
query. Remember that rules effectively work on the query strings
themselves, so to impact that update you'd have to have a rule on
account_login. No rule on a child table will matter.
--
Jim Nasby jim(at)nasby(dot)net
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel van Ham Colchete | 2007-06-22 21:23:44 | Possible bug (or I don't understand how foreign keys should work with partitions) |
| Previous Message | jef peeraer | 2007-06-22 20:59:13 | permission denied for schema |