> The alphabetical ordering would change the order, but only with respect to
> the new constraint and existing ones not between the existing ones. The
> advantage here is that making a trigger fire before an existing one is
> easy, since you can name before it.
>
> The oid ordering has the property that the triggers would by default run
> in creation order. Creating a new trigger would always put it at the end
> unless you've wrapped oids which is nicer than having to worry about
> interactions between the new trigger and existing ones based on where it
> is (although you have to do that now), however putting a trigger before
> an existing one means dropping and recreating one or more of your existing
> triggers... all of the ones from where you want to put it in the order to
> the last one.
Good points. It is a tradeoff between making things stable for people
who don't notice the order vs. making it easy to define the ordering.
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
