Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Squash migrations through v3.6 #13647

Closed
jeremystretch opened this issue Aug 31, 2023 · 1 comment
Closed

Squash migrations through v3.6 #13647

jeremystretch opened this issue Aug 31, 2023 · 1 comment
Assignees
@jeremystretch
Labels
status: accepted This issue has been accepted for implementation type: housekeeping Changes to the application which do not directly impact the end user
Milestone
v4.0

Comments

@jeremystretch
Copy link
Member

Proposed Changes

Squash all existing migrations up to the v3.6.0 release. (This is a repeat of what we did for the v3.0 release under #6471.)

Justification

Squashing migrations optimizes necessary changes to the database schema and reduces installation time.
@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation type: housekeeping Changes to the application which do not directly impact the end user labels Aug 31, 2023
@jeremystretch jeremystretch added this to the v4.0 milestone Aug 31, 2023
@jeremystretch jeremystretch changed the title Squash migrations through v3.5 Squash migrations through v3.6 Sep 25, 2023
@jeremystretch jeremystretch self-assigned this Jan 5, 2024
@arthanson arthanson mentioned this issue Jan 12, 2024
Closed
@jeremystretch jeremystretch mentioned this issue Jan 18, 2024
Merged
jeremystretch added a commit that referenced this issue Jan 19, 2024
@jeremystretch
Closes #13647: Squash all migrations prior to v3.7 (#14853)
874685f 
* Regenerate pre-v3.7 migrations

* Annotate replaced migrations

* Rename dependencies; remove FeatureQuery references

* Add missed replacement
jeremystretch added a commit that referenced this issue Jan 22, 2024
@jeremystretch
Revert "Closes #13647: Squash all migrations prior to v3.7 (#14853)"
222388b 
This reverts commit 874685f.
@jeremystretch
Copy link
Member Author

Re-opening this as there's an issue with the way squashed migrations are split:

django.db.migrations.exceptions.InconsistentMigrationHistory: Migration circuits.0004_squashed is
applied before its dependency circuits.0003_squashed on database 'default'.

@jeremystretch jeremystretch mentioned this issue Jan 24, 2024
Merged
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 25, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@jeremystretch jeremystretch

Labels
status: accepted This issue has been accepted for implementation type: housekeeping Changes to the application which do not directly impact the end user
Projects
None yet
Milestone
v4.0
Development

No branches or pull requests
1 participant
@jeremystretch