Re: Rules/Trigges Trade-offs
От | Bruce Momjian |
---|---|
Тема | Re: Rules/Trigges Trade-offs |
Дата | |
Msg-id | 200212062330.gB6NUDl20018@candle.pha.pa.us обсуждение исходный текст |
Ответ на | Re: Rules/Trigges Trade-offs (Josh Berkus <josh@agliodbs.com>) |
Ответы |
Re: Rules/Trigges Trade-offs
|
Список | pgsql-sql |
Josh Berkus wrote: > > Bruce, Richard, > > > Triggers are mostly for testing/modifying the row being > > inserted/updated, while rules are better for affecting other rows or > > other tables. > > Hmmm. Thought that there were also some other criteria: > > 1) Rules can't use indexes to do their processing, so Rules which query large > secondary tables can be a bad idea (maybe this has changed?) I don't think this is true. Rewrite is before optimizer so it should be optimized just the same. > > 2) Only Rules can "DO INSTEAD"; thus, only Rules are good for defining > Read/Write views. True. > 3) There are no AFTER Rules, making, for example, a rule with a table check on > the new data impractical, so you'd want to use Triggers or Constraints We have changed ordering in 7.3 where I think INSERT rules are _after_ the insert. -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001+ If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania19073
В списке pgsql-sql по дате отправления: