*The transaction that his procedure runs in* (call it ThisTransaction)
indeed DOES read the uncommitted inserts that its statements have executed.
A transaction sees all of its own work. Have you been handling this hot
thing all this time, without knowing? ;-)

It seems that he is perhaps confused, thinking that the steps through a
procedure and the involved trigger actions are in some way queued and
deferred until the commit. That is not what happens. Instead, an action is
executed in its actual sequence and execution proceeds onward inexorably.

When everything is done, control returns to the client that owns the
transaction.
-- If the client commits the transaction, exactly the same changes that the
(now defunct) transaction could see before are now visible to other
transactions.
-- If the client rolls back the transaction, then NO changes, whether
effected by the procedure or by triggers, will be visible to any
transaction.

./hb

---

Many thanks for your responses.



Dear Helen, will there be a firebird book for version 2.5, perhaps in German
Language too? There are other recommend books available for firebird?



Thank you all for the great work!



Best regards.



Olaf







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