etl: make all migrations idempotent#196
Closed
raymondjacobson wants to merge 1 commit intorj/etl-parity-testfrom
Closed
etl: make all migrations idempotent#196raymondjacobson wants to merge 1 commit intorj/etl-parity-testfrom
raymondjacobson wants to merge 1 commit intorj/etl-parity-testfrom
Conversation
- Wrap etl_proof_status enum creation in DO/EXCEPTION block - Add DROP TRIGGER IF EXISTS before CREATE TRIGGER - Add DROP MATERIALIZED VIEW IF EXISTS before CREATE MATERIALIZED VIEW - Name materialized view indexes for IF NOT EXISTS support This ensures migrations can run safely against databases where these objects already exist (e.g., production clones). Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This was referenced Apr 3, 2026
Closed
Closed
Contributor
Author
Contributor
Author
|
Superseded by #200 (squash merged) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.

This ensures migrations can run safely against databases where
these objects already exist (e.g., production clones).
Co-Authored-By: Claude Opus 4.6 noreply@anthropic.com