Re: "strange" rule behavior with nextval on new.* fields - Mailing list pgsql-bugs

From Tom Lane
Subject Re: "strange" rule behavior with nextval on new.* fields
Date
Msg-id 19593.1100271897@sss.pgh.pa.us
Whole thread Raw
In response to Re: "strange" rule behavior with nextval on new.* fields  (Michael Fuhr <mike@fuhr.org>)
Responses Re: "strange" rule behavior with nextval on new.* fields
List pgsql-bugs
Michael Fuhr <mike@fuhr.org> writes:
> This comes up often enough that maybe it warrants a "Caveats with
> Rules" section in "The Rule System" chapter and a link to that
> section in the CREATE RULE documentation, as well as mention in the
> FAQ.

Yeah.  I have also thought about reorganizing the docs so that triggers
are presented as being simpler than rules (come first, etc).  I think
right now the docs actively mislead newbies into choosing rules in cases
where triggers would be much better.

            regards, tom lane

pgsql-bugs by date:

Previous
From: Michael Fuhr
Date:
Subject: Re: "strange" rule behavior with nextval on new.* fields
Next
From: "Alexander M. Pravking"
Date:
Subject: Broken CIDR: no fix in 7.4.6?