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 Trigger runtime meta model #11248

Closed
44 tasks done
lukaseder opened this issue Jan 18, 2021 · 0 comments
Closed
44 tasks done

Add Trigger runtime meta model #11248

lukaseder opened this issue Jan 18, 2021 · 0 comments

Comments

@lukaseder
Copy link
Member

lukaseder commented Jan 18, 2021

#6956 introduces DDL statement support on TRIGGER.

A separate task is to implement the entire runtime meta model, import, export, and interpretation of it

Tasks

Follow up tasks

References:


See also:
https://stackoverflow.com/q/47969132/521799

@lukaseder lukaseder added this to the Version 3.15.0 milestone Jan 18, 2021
@lukaseder lukaseder added this to To do in 3.14 More procedural support via automation Jan 18, 2021
lukaseder added a commit that referenced this issue Jul 4, 2023
lukaseder added a commit that referenced this issue Jul 11, 2023
- Added Meta::getTriggers and ::filterTriggers with impls in:
  - InformationSchemaMetaImpl
  - AbstractMeta
  - CatalogMetaImpl
  - FilteredMeta
- Added XMLDatabase and XMLGenerator implementations
lukaseder added a commit that referenced this issue Jul 11, 2023
lukaseder added a commit that referenced this issue Nov 23, 2023
…triggers

This includes:

- [#11248] SQL Server trigger meta data support
lukaseder added a commit that referenced this issue Nov 24, 2023
This includes:

- [#15872] QOM.CreateTrigger and related API should work with new org.jooq.Trigger type
lukaseder added a commit that referenced this issue Nov 24, 2023
We have integration tests covering all API with @NotNull annotations to make sure they never return null. These tests fail if we construct a CREATE TRIGGER statement with null arguments using the QOM API, which we're doing implicitly as the mutator methods can only set one value at a time.
3.14 More procedural support automation moved this from To do to Done Nov 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

1 participant