On Sat, 23 Nov 2002 [EMAIL PROTECTED] wrote: > Luís Mota ([EMAIL PROTECTED]) reports a bug with a severity of 2 > The lower the number the more severe it is. > > Short Description > Condition on rule is not respected. > > Long Description
> I think I spoted a bug while developing a database. To better > understand if this was really a bug, I developed a small example that > I include further down. > > The question is that I want to write a rule that inserts a record in a > second table (table B) each time a record is inserted on a first table > A, and vice-versa. > > To do this, I wrote two insert rules. To avoid a dead-lock, I created > a boolean field which serves as guard to the insertion. Unfortunatly, > I think that the condition I set up in the insert rules is not > respected. The rule where condition does not stop the rule from being expanded. It changes the rows that are acted upon, but not whether or not the rule action occurs. If you're looking to do something like that, you probably actually need a trigger. ---------------------------(end of broadcast)--------------------------- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
