#33899: migrations.RemoveField causes OperationalError "no such column" upon
migration
-------------------------------------+-------------------------------------
Reporter: cessor | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 4.1
Severity: Normal | Resolution:
Keywords: Migration Sqlite | Triage Stage:
Docker | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by cessor):
Replying to [comment:2 Mariusz Felisiak]:
> I'm really puzzled. I cannot reproduce this issue manually, but `make
red` crashes.
Thank you for giving this a try. I investigated this some further and
realized that my manual description is not precise enough to reproduce the
error. The example I attached uses a SlugField, but the error does not
occur with other field types, such as CharFields. I noticed that
SlugFields set `db_index=True` by default (See Link 1), and could
reproduce the bug with other fields when setting `db_index=True`. I will
change the bug description accordingly.
Links:
- 1: SlugField:
[https://github.com/django/django/blob/main/django/db/models/fields/__init__.py#L2301]
--
Ticket URL: <https://code.djangoproject.com/ticket/33899#comment:3>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018272d3e6da-a9d345a1-5f67-40ef-b07c-27a485f141b0-000000%40eu-central-1.amazonses.com.
