Use drop trigger if exists to support pg12 #657
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.
What kind of change does this PR introduce?
Bug fix
What is the current behavior?
create or replace trigger
only available up from PG14. When I connect to PG12, migration fails asstorage/migrations/tenant/0026-objects-prefixes.sql
Lines 148 to 169 in 37be2a3
storage/migrations/tenant/0035-add-insert-trigger-prefixes.sql
Lines 2 to 8 in 37be2a3
contains unsupported syntax.
What is the new behavior?
Use
drop trigger if exists / create trigger
instead ofcreate or replace trigger
to support pg12.Additional context
Add any other context or screenshots.