Subject | AW: AW: [firebird-support] transaction the hundreth |
---|---|
Author | Olaf Kluge |
Post date | 2011-06-10T09:21:44Z |
Yes you are wrong - or at least your expectation is wrong - , the trigger
is executed at INSERT and not deferred until commit which you seem to
expect. So it is executed as soon as you do the INSERT into the table. As
you haven't inserted into the secondary tables yet (those follow after that
INSERT into A), nothing is found at that time.
You either need to reorder your inserts, have the processing be triggered
by inserts into B and/or C, or use an entirely different method for
triggering this processing.
Mark
--
Hello Mark,
okay, I’m wrong. I thought the trigger sees the record until the transaction is completed. But the action is executed immediately without waiting until the transaction and all other records are complete.
Thanks.
Have a nice weekend.
Olaf
[Non-text portions of this message have been removed]
is executed at INSERT and not deferred until commit which you seem to
expect. So it is executed as soon as you do the INSERT into the table. As
you haven't inserted into the secondary tables yet (those follow after that
INSERT into A), nothing is found at that time.
You either need to reorder your inserts, have the processing be triggered
by inserts into B and/or C, or use an entirely different method for
triggering this processing.
Mark
--
Hello Mark,
okay, I’m wrong. I thought the trigger sees the record until the transaction is completed. But the action is executed immediately without waiting until the transaction and all other records are complete.
Thanks.
Have a nice weekend.
Olaf
[Non-text portions of this message have been removed]