Ways to get a list of tables affected by a transaction in a Trace Plugin?
21 views
Skip to first unread message
Maxim Kryukov
unread,
May 24, 2026, 1:24:25 PM (yesterday) May 24
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to firebird-devel
Hi all, In my custom Trace Plugin I would like to collect the names of tables whose data has been modified in a transaction between transaction start and commit events. I see two methods: 1) install triggers on insert/update/delete for every table and proccess trigger run event; and 2) process execute statement events to parse sql statements; not sure how to handle stored procedures (dive into BLR?), more confused about handling external functions. Are there any other ways to achieve this within a Trace Plugin?
Vlad Khorsun
unread,
May 24, 2026, 2:26:59 PM (yesterday) May 24
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to firebir...@googlegroups.com
24.05.2026 20:24, 'Maxim Kryukov' via firebird-devel:
Use per-table counters that is available in PerformanceInfo returned by TraceTransaction.getPerf();
Regards,
Vlad
mxck
unread,
May 24, 2026, 2:39:08 PM (yesterday) May 24
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to firebir...@googlegroups.com
Thank you very much indeed, my fault I missed it. Hope PerformanceInfo
has enough info in FB 3.0.8 tag, will know soon.