#33899: migrations.RemoveField causes OperationalError "no such column" upon
migration
-------------------------------------+-------------------------------------
Reporter: cessor | Owner: nobody
Type: Bug | Status: new
Component: | Version: 4.1
Migrations | Keywords: Migration Sqlite
Severity: Normal | Docker
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
== 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:
0. Install django 4.1
1. Create a new project
2. Create an app
3. Install app in project
4. Create a model
5. Add field on model
6. Make migrations
7. Remove field
8. Make migrations
The migration should fail.
--
Ticket URL: <https://code.djangoproject.com/ticket/33899>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/010701826e5c59e9-e971d425-327d-4d90-935a-e51d5f148edf-000000%40eu-central-1.amazonses.com.
