Staging #741
Merged
Staging #741
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
Drop orphaned tables left over from Django migration: - 12 Django auth/admin tables (django_*, auth_*, account_*, authtoken_*) - 9 social auth tables (social_auth_*, socialaccount_*) - 17 legacy API tables (api_eapuser, api_assurancecase, api_evidence, etc.) - 1 websockets table Data was already migrated to Prisma-managed tables. Old-to-new ID mappings preserved in legacy_mappings table. Resolves: AssurancePlatform-jdr
Rename 4 Django-era tables to consistent snake_case naming: - api_casestudy → case_studies - api_casestudy_assurance_cases → case_study_published_cases - api_casestudyfeatureimage → case_study_images - api_publishedassurancecase → published_assurance_cases Also renames all associated indexes, constraints, and sequences. Resolves: AssurancePlatform-at5
- Rename 4 legacy Django tables to clean conventions:
api_casestudy → case_studies
api_casestudy_assurance_cases → case_study_published_cases
api_casestudyfeatureimage → case_study_images
api_publishedassurancecase → published_assurance_cases
- Add comprehensive doc comments to Prisma schema models
- Configure prisma-dbml-generator for schema documentation
- Set manyToMany=false to prevent spurious CommentThread table
Remove unused pessimistic locking feature:
- Drop lock_uuid, locked_by_id, locked_at columns from assurance_cases
- Remove /api/cases/[id]/lock API route
- Remove lock service functions and SSE event types
- Update types, actions, and test fixtures
The locking feature was fully implemented but never called from the
frontend. Real-time collaboration uses SSE events instead.
The entrypoint script was failing because it tried to query api_eapuser to check if data migration was needed, but that table was dropped in migration 20260110000000_remove_legacy_django_tables. Now checks if api_eapuser exists first via information_schema before attempting the data migration check.
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.
No description provided.