Re: A problem in inheritance
- 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: Fri, 22 Jun 2007 16:10:51 -0500
- Message-id: <9500CE34-4019-40E1-9859-34243AEEC261(at)decibel(dot)org>
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)
Home |
Main Index |
Thread Index