Why Find schema trigger will execute before session trigger?

[GaneshP]

Hi,
Can any one explain
Why Find schema trigger will execute before session trigger? if find trigger defined in schema and session level.

 

[jdpjamesp]

Because it has to happen in some order and that's the order that was chosen. Probably.
Is there a specific problem you are trying to solve?

 

[GaneshP]

Because it has to happen in some order and that's the order that was chosen. Probably.
Is there a specific problem you are trying to solve?

I want understand what is the reason behind in case of find
Normally triggers will execute first session and schema level for create,delete,assign,write except find trigger on same table

In case of find trigger first schema and session will execute

can you please explain or give example is there any specific reason for find trigger to execute different way?

 

[RealHeavyDude]

Probably there is no other reason than somebody designed it that way.

Unless you have a sound business case - using find triggers is the road to hell. You will hammer the database and produce unnecessary network round trips.

 

[TomBascom]

Consider a case where FIND triggers are being used to provide security (i.e. to prevent unauthorized reads). In that case it makes an awful lot of sense for the schema trigger to fire first.

Also - RHD isn't kidding. FIND triggers are the road to performance hell. If you are going to use them you had better have a VERY good reason. And even then you should reconsider.

 

[Marco Mendoza]

Hi,
Can any one explain
Why Find schema trigger will execute before session trigger? if find trigger defined in schema and session level.

I suggest you to write the question to Forum - OpenEdge Development - Progress Community, it is common to receive responses from Progress staff and it seems only they know why is designed on this way.