Database-level triggers related to TRANSACTION events (i.e. start, commit and rollback) do not take in account their POSITION index (when more than one trigger for the same event type is defined) [CORE5542] #5810
Assignees
Comments
Modified by: @pavel-zotovAttachment: db-level-triggers-for-Tx-events-ignore-position-index-from-their-ddl.7z [ 13116 ] |
Modified by: @asfernandesassignee: Adriano dos Santos Fernandes [ asfernandes ] |
Modified by: @asfernandesstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 4.0 Alpha 1 [ 10731 ] Fix Version: 3.0.3 [ 10810 ] |
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Resolved [ 5 ] QA Status: No test => Done successfully Test Details: Test was splitted on following separate .fbt (one per each event): core_5542-db_attach.fbt |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Submitted by: @pavel-zotov
Attachments:
db-level-triggers-for-Tx-events-ignore-position-index-from-their-ddl.7z
Run scripts from attached .7z (or just see their logs - also in this attach).
You will see that only triggers for CONNECT / DISCONNECT event honour the index that was specified in POSITION clause.
"
Commits: 67222d7 8263711
====== Test Details ======
Test was splitted on following separate .fbt (one per each event):
core_5542-db_attach.fbt
core_5542-db_detach.fbt
core_5542-tx_commit.fbt
core_5542-tx_rollback.fbt
core_5542-tx_start.fbt
The text was updated successfully, but these errors were encountered: