chore: remove obsolete candidate job order status type tables#772
Open
anonymoususer72041 wants to merge 2 commits into
Open
Conversation
anonymoususer72041
changed the title
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
1 participant
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 removes obsolete candidate job order status type table handling from the current schema and install backup flow.
The misspelled
candidate_jobordrer_status_typetable is no longer created by the schema snapshot. A new install schema step drops this table and also keeps a defensive cleanup for the historically referencedcandidate_joborder_status_typename, so existing installations are cleaned up during schema updates if either legacy table is present.The dedicated backup exclusion for
candidate_joborder_status_typeis removed as well. Since this legacy table name is now covered by the install schema cleanup path, it no longer needs to be preserved as a special case in database backups.