Opened 3 years ago
Last modified 3 years ago
#33899 closed Bug
migrations.RemoveField causes OperationalError "no such column" upon migration — at Initial Version
| Reported by: | cessor | Owned by: | nobody |
|---|---|---|---|
| Component: | Migrations | Version: | 4.1 |
| Severity: | Release blocker | Keywords: | Migration Sqlite |
| Cc: | Triage Stage: | Ready for checkin | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
| Pull Requests: | |||
Description ¶
Description ¶
I encountered the following error with django 4.1 in my Gitlab CI/CD Pipeline. When I bumped django versions from 4.0.7 to 4.1. my pipeline broke during the testing stage; specifically during db migrations. I have not changed the any other source code.
Steps to reproduce ¶
Minimal example attached. Run make green to see that it works with 4.0.7, run make red to see that it does not work with 4.1.
Manual steps:
- Install django 4.1
- Create a new project
- Create an app
- Install app in project
- Create a model
- Add field on model
- Make migrations
- Remove field
- Make migrations
The migration should fail.
Note:
See TracTickets
for help on using tickets.
Minimal Example