Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add org.jooq.Trigger to support custom callbacks to be configured #1691

Closed
lukaseder opened this issue Aug 10, 2012 · 1 comment
Closed

Add org.jooq.Trigger to support custom callbacks to be configured #1691

lukaseder opened this issue Aug 10, 2012 · 1 comment

Comments

@lukaseder
Copy link
Member

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.

Some examples:

@lukaseder
Copy link
Member Author

This feature is better represented by the new client side computed columns feature: #13444

3.17 Other improvements automation moved this from To do to Done Jun 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Development

No branches or pull requests

1 participant