Support Instead of Trigger On Views Pg16_1 #2207
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Currently Postgres does not support Instead of Trigger On Views for DML queries.
On running such a query on VIEW, query rewriting substitutes view with underlying base table.
Added a hook for skipping the substitution for DML query on the VIEW.
This change will add support for Instead of Triggers for DML queries when using Babelfish.
Task: BABEL-2170/BABEL-4532/BABEL-4514
Engine PR 16_1: babelfish-for-postgresql/postgresql_modified_for_babelfish#280
Engine PR 15: babelfish-for-postgresql/postgresql_modified_for_babelfish#272
Extensions PR 15: #2158
Issues Resolved
BABEL-2170/BABEL-4532/BABEL-4514
Test Scenarios Covered
Instead of Trigger (IOT) on View for Insert/Update/Delete queries
Transition tables inside IOT on View
IOT calling itself. IOT A <-> IOT A
IOT A <-> IOT B
IOT with transition tables
IOT Cross database
IOT Cross Schema
IOT for Transaction, Commit, Rollback, Rollback to Savepoint
IOT for Bulk insert
Same name trigger not allowed for View/Table
DROP Trigger cross Schema
Check List
By submitting this pull request, I confirm that my contribution is under the terms of the Apache 2.0 and PostgreSQL licenses, and grant any person obtaining a copy of the contribution permission to relicense all or a portion of my contribution to the PostgreSQL License solely to contribute all or a portion of my contribution to the PostgreSQL open source project.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.