fix: changed migration script#52
Merged
Merged
Conversation
Alam-2U
force-pushed
the
ealam/migration_script_changes
branch
from
1cdb141 to
c884ced
Compare
santhosh-apphelix-2u
approved these changes
May 19, 2026
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
2 participants
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.
Description
During MongoDB → MySQL migration validation in stage, multiple data consistency issues were identified. This PR updates the migration scripts for production and adds backfill commands to correct the affected stage data.
Changes Included
Fixed
created_atandupdated_atfields inforum/backends/mysql/models.pyto usedefault=timezone.nowinstead ofauto_now_add=True/auto_now=True, preventing original timestamps from being overwritten during migration.Added missing
closed_byandreasonfields to the migration script so the data is migrated correctly from MongoDB to MySQL.Added backfill support for
author_usernamefor older migrated records where the field remainedNULLbecause the column was introduced after the initial July/October migrations.Added commands/scripts to backfill all three issues in the stage environment before production rollout.
Tickets
COSMO2-923
COSMO2-925
COSMO2-936