Add afterSQL
attribute to execute a query after the JDBC trigger condition was satisfied - ideally, in the same transaction
#149
Labels
enhancement
New feature or request
Feature description
To avoid never-ending loops in JDBC triggers, users typically need to modify the data in a separate task to avoid the same condition being fired twice (UPDATE or DELETE rows with the same WHERE condition from the trigger sql).
Users currently need to define an extra task:
It would be great to simplify such a pattern using
afterSQL
property (name TBD - could bepostTriggerSql
):The text was updated successfully, but these errors were encountered: