Fix database schema drift and restore foreign key integrity #160
+111
−5
Conversation
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
Update SQLAlchemy models to explicitly define `ON DELETE` behaviors (CASCADE/SET NULL) matching the database schema. Add migration 0060 to: - Clean up orphaned newsletter references in parsed_dive_trips - Remove duplicate/conflicting foreign keys in production - Normalize api_keys indexes - Standardize foreign keys across local and production environments This resolves persistent Alembic drift and IntegrityError 1452 in production.
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.
Update SQLAlchemy models to explicitly define
ON DELETEbehaviors (CASCADE/SET NULL) matching the database schema. Add migration 0060 to:This resolves persistent Alembic drift and IntegrityError 1452 in production.