You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In legacy environments where new database triggers cannot be implemented easily, jOOQ shall offer custom trigger functionality, mimicking commonly known database trigger functionality.
These jOOQ triggers allow for intercepting basic DML statements, such as DELETE, INSERT, UPDATE. More sophisticated DML statements, such as MERGE, INSERT ... SELECT, INSERT ... ON DUPLICATE KEY UPDATE may not be supported. Batch execution may not be supported either, or the batch statement may be split into several single statements.
On interception, i.e. on firing of a trigger, the trigger may execute custom Java code (including custom SQL / jOOQ code) BEFORE, AFTER or INSTEAD OF the intercepted DML statement.
In addition to what SQL databases offer, this trigger API also allows for intercepting SELECT statements, and perform BEFORE, AFTER or INSTEAD OF actions on those.
In legacy environments where new database triggers cannot be implemented easily, jOOQ shall offer custom trigger functionality, mimicking commonly known database trigger functionality.
These jOOQ triggers allow for intercepting basic DML statements, such as
DELETE
,INSERT
,UPDATE
. More sophisticated DML statements, such asMERGE
,INSERT ... SELECT
,INSERT ... ON DUPLICATE KEY UPDATE
may not be supported. Batch execution may not be supported either, or the batch statement may be split into several single statements.On interception, i.e. on firing of a trigger, the trigger may execute custom Java code (including custom SQL / jOOQ code)
BEFORE
,AFTER
orINSTEAD OF
the intercepted DML statement.In addition to what SQL databases offer, this trigger API also allows for intercepting
SELECT
statements, and performBEFORE
,AFTER
orINSTEAD OF
actions on those.Some examples:
The text was updated successfully, but these errors were encountered: