"Peter Marius" <[EMAIL PROTECTED]> writes:
> I created a view on all entries with stop=null.
> The DB-Interaction should be done over the view,
> so I added rules for INSERT, UPDATE an DELETE.
> Insert and Update work fine, but the DELETE_RULE
> stopps after the first UPDATE statement in the Rule-Body,
> any further statements are ignored!!
Once you change the stop field to not be null, the row's no longer part
of the view, so there's nothing to update. You need to re-order the
operations (and, probably, combine the two UPDATE commands) so that you
don't remove the row from the view until the last step.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
