-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
fix update event trigger & dropping triggers on run_sql
(fix #3803, #3784)
#3833
Conversation
Deploy preview for hasura-docs ready! Built with commit 6ae1d91 |
Review app for commit 6ae1d91 deployed to Heroku: https://hge-ci-pull-3833.herokuapp.com |
6ae1d91
to
8a7f3d8
Compare
Review app for commit 8a7f3d8 deployed to Heroku: https://hge-ci-pull-3833.herokuapp.com |
8a7f3d8
to
76267a6
Compare
Review app for commit 76267a6 deployed to Heroku: https://hge-ci-pull-3833.herokuapp.com |
Review app for commit 0a654bb deployed to Heroku: https://hge-ci-pull-3833.herokuapp.com |
Review app https://hge-ci-pull-3833.herokuapp.com is deleted |
…#3803 hasura#3784 (hasura#3833) Co-authored-by: Vamshi Surabhi <0x777@users.noreply.github.com>
Description
This PR fixes the following issues:-
#3784 - Event triggers are lost on
run_sql
DDL queries.#3803 - Event trigger is being wiped on recreating
Affected components
Related Issues
#3784 #3803
Solution and Design
3784:- Recreate all event triggers at the end of a
run_sql
DDL query.3803:- Move delete trigger logic to build schema cache. If ops definition changes, the trigger is deleted (if exists) and created again with updated definition.
Steps to test and verify
run_sql
query with DDL statement shouldn't drop any trigger procedures in thehdb_views
schemahdb_views
schema.Limitations, known bugs & workarounds
Server checklist
Catalog upgrade
Does this PR change Hasura Catalog version?
Metadata
Does this PR add a new Metadata feature?
GraphQL
Breaking changes