patrickTingen
commented
1 year ago Hi Jeroen,
Although I am a bit reluctant to add new settings, this sounds like a good candidate to me. I will add an extra setting to allow replication triggers.
-- Patrick Tingen
Op ma 17 apr 2023 om 15:09 schreef Jeroen Eeuwes @.***>:
In the datadigger there are several lines which disable the load triggers. If you use the database replication triggers this means the replication for that change is lost.
This is resolved by changing all the DISABLE-LOAD-TRIGGERS(FALSE) to DISABLE-LOAD-TRIGGERS(TRUE).
In generate-Bulk-Delete.w and generate-DumpLoad-Procedure.w there is some code generation which needs to be amended. The lines with "DISABLE TRIGGERS FOR LOAD" should be changed to "DISABLE TRIGGERS FOR LOAD ... ALLOW-REPLICATION ...".
Or perhaps there should be a setting to (dis)allow the replication triggers?
— Reply to this email directly, view it on GitHub https://github.com/patrickTingen/DataDigger/issues/100, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABN3AHLR5TCLAGD634HQJ6TXBU6JFANCNFSM6AAAAAAXBFLECU . You are receiving this because you are subscribed to this thread.Message ID: @.***>
In the datadigger there are several lines which disable the load triggers. If you use the database replication triggers this means the replication for that change is lost.
This is resolved by changing all the DISABLE-LOAD-TRIGGERS(FALSE) to DISABLE-LOAD-TRIGGERS(TRUE).
In generate-Bulk-Delete.w and generate-DumpLoad-Procedure.w there is some code generation which needs to be amended. The lines with "DISABLE TRIGGERS FOR LOAD" should be changed to "DISABLE TRIGGERS FOR LOAD ... ALLOW-REPLICATION ...".
Or perhaps there should be a setting to (dis)allow the replication triggers?