-
-
Notifications
You must be signed in to change notification settings - Fork 4.5k
chore(commits): Delete unused dual write commit tables #102506
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
2822b79 to
2642a0b
Compare
Follow up migration to delete these from the database.
f81980f to
55288c1
Compare
|
This PR has a migration; here is the generated SQL for for --
-- Delete model Commit
--
DROP TABLE "releases_commit" CASCADE;
--
-- Delete model CommitFileChange
--
DROP TABLE "releases_commitfilechange" CASCADE; |
|
|
||
| operations = [ | ||
| SafeDeleteModel(name="Commit", deletion_action=DeletionAction.DELETE), | ||
| SafeDeleteModel(name="CommitFileChange", deletion_action=DeletionAction.DELETE), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@wedamija Do you want DeletionAction.MOVE_TO_PENDING first?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Already handled in 0002. Also, jfyi, ci will complain if someone attempts to delete before doing MOVE_TO_PENDING first
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good to know!
Follow up migration to delete these from the database.
Follow up migration to delete these from the database. Leaving this in draft until the code removal deploys