Skip to content

PR 4 Couch to sql migration for CommCareBuild - #38078

Open
jingcheng16 wants to merge 1 commit into
jc/couch-to-sql-3from
jc/couch-to-sql-4
Open

PR 4 Couch to sql migration for CommCareBuild#38078
jingcheng16 wants to merge 1 commit into
jc/couch-to-sql-3from
jc/couch-to-sql-4

Conversation

@jingcheng16

Copy link
Copy Markdown
Contributor

Product Description

Technical Summary

PR 1: #37954
PR 2: #37955
PR 3: #37956

The last PR of couch to sql migration for CommCareBuild. PR 3 only dropped the couch_id column from Django model, and this PR is to remove it from the sql database.
This PR should not be merged until PR 3 is merged for 6 weeks.

Feature Flag

Safety Assurance

Safety story

Tested locally. Straightforward migration.

Automated test coverage

QA Plan

Migrations

  • The migrations in this code can be safely applied first independently of the code. Pay particular attention to backward incompatible operations like RemoveField, RenameField, RemoveConstraint, and others described here that can cause errors when migrations are applied to a live database.

#37956

Rollback instructions

  • This PR can be reverted after deploy with no further considerations

Labels & Review

  • Risk label is set correctly
  • The set of people pinged as reviewers is appropriate for the level of risk of the change

@dimagimon dimagimon added the reindex/migration Reindex or migration will be required during or before deploy label Aug 28, 2026
@jingcheng16 jingcheng16 added the Open for review: do not merge A work in progress label Aug 28, 2026
@jingcheng16
jingcheng16 marked this pull request as ready for review August 28, 2026 13:24
@jingcheng16 jingcheng16 added the product/invisible Change has no end-user visible impact label Aug 28, 2026

@millerdev millerdev left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you intend to update the documentation about scenarios where a PR 4 is necessary?

@jingcheng16

Copy link
Copy Markdown
Contributor Author

@millerdev Will do! Though I almost forget about it. 😂 @gherceg let's do it on monday!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Open for review: do not merge A work in progress product/invisible Change has no end-user visible impact reindex/migration Reindex or migration will be required during or before deploy

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants