On Fri, 27 May 2005, Tom Lane wrote:
Same old same old: as soon as you've deleted from offer_mutable, there
is no row in the view with the given offer_id; and since OLD is a macro
for the view, the second delete finds nothing to do.
Oh, now I'm starting to see how this behavior does make sense
Curt Sampson <[EMAIL PROTECTED]> writes:
> CREATE VIEW offer AS
> SELECT * FROM offer_immutable NATURAL JOIN offer_mutable;
> In a transaction, when I try to commit, this does not work:
> CREATE OR REPLACE RULE offer_delete AS
> ON DELETE TO offer DO INSTEAD (
> DE
I've got a table I've split into two, a portion that can be modified
under normal circumstances, and a portion that can't be. (In a testing
mode they both can be, but in production the user IDs doing the work
don't have update or delete access on the immutable portion. BTW, I'm
open to better way
