That sounds like a nice suggestion. I guess it could get rid of most of the
issues I forsee. I should follow that for my cases too.
I guess we can live without an ORDER clause.
Thanks everyone for helping.
Sameer Kumar wrote:
> If I have a trigger which add primary key to my inserted row
> ("before trigger"). Now if I plan to create new set of triggers
> for AUDITING or replication (where either I have no flexibility
> of choosing a name or the trigger name has to follow a standard),
> then I need
>
>
But with certain packaged products who create their own triggers, I won't
>> have control over this.
> I don't have a lot of sympathy for that argument. If the product is
> capable of creating Postgres-compatible triggers at all, it should be
> aware that the name is a significant property,
Sameer Kumar writes:
> Is it possible for me to define the order in which triggers will be fired?
Sure: choose their names so that their alphabetical ordering is the
firing order you want. But I see you knew that.
> But with certain packaged products who create their own triggers, I won't
> hav
Sameer Kumar wrote
> Hi,
>
> Is it possible for me to define the order in which triggers will be fired?
>
> So far what I have understood from PostgreSQL documentation, in order to
> fire 2 triggers in sequence (say trigger1 and trigger2) on a table, I need
> to name them in that way.
> But with
Hugo wrote:
Hi, how can I tell in which order are triggered different triggers on the
same table, let me explain ,
I have three triggers for table A, all of then are intended for "before
insert" on the table, in ASA I can tell the Db in which order I want the
triggers to fire, is there an equival
Terry Lee Tucker wrote:
On Monday 10 April 2006 05:09 pm, Hugo saith:
Hi, how can I tell in which order are triggered different triggers on the
same table, let me explain ,
I have three triggers for table A, all of then are intended for "before
insert" on the table, in ASA I can tell the Db in w
On Monday 10 April 2006 05:09 pm, Hugo saith:
> Hi, how can I tell in which order are triggered different triggers on the
> same table, let me explain ,
> I have three triggers for table A, all of then are intended for "before
> insert" on the table, in ASA I can tell the Db in which order I want t
> Hi, how can I tell in which order are triggered different triggers on the
> same table, let me explain ,
> I have three triggers for table A, all of then are intended for "before
> insert" on the table, in ASA I can tell the Db in which order I want the
> triggers to fire, is there an equivalent
"Alex Bolenok" <[EMAIL PROTECTED]> writes:
> peroon=# INSERT INTO t_foo (foo_value) VALUES (2000);
> NOTICE: fn_foo_ains: Start
> NOTICE: fn_foo_ains: End
> NOTICE: fn_bar_ains: Start
> NOTICE: fn_bar_ains: End
Looking at the code, it seems that all AFTER triggers are implicitly
handled as DE
10 matches
Mail list logo
