Hi,

triggers always execute in the client side transaction context.

eg: client: start transaction
- client: insert record
- server: trigger fires in client transaction context
- client: commit/rollback

Martijn Tonies
InterBase Workbench - the developer tool for InterBase and Firebird
http://www.interbaseworkbench.com

Hi
I just read the embedded sql guide about sp's and transactions.
It almost answers my question but some verification would be
appreciated. If the sp gets called by the db itself what is the
default transaction and how would you change it. Eg If I call
a sp via trigger.

Groete
Gerhardsu

> Hi
> My scenario will explain the best.
>
> procedure dosomething
> for select * from TableA do
> //externally somebody adds/remove/change something to tableA.
> //I do the the same selection again.
> for select * from TableA do
>
> will the second for loops be the same as the first one.
> How does transactions works in the context of stored procedures?
>
> Groete
> Gerhardus

[Non-text portions of this message have been removed]