Dear Tom,
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.
ISTM that having SQL as a language for trivial triggers would also help.
RULEs are SQL, although triggers must be C or PL*.
That could also be a candidate TODO, next to "improve the doc"?
Thanks for your answer,
--
Fabien Coelho - [EMAIL PROTECTED]
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
