#32787: ContentTypes are created instead of renamed when using
SeparateDatabaseAndState
-------------------------------------+-------------------------------------
Reporter: David Seddon | Owner: nobody
Type: New feature | Status: closed
Component: Database layer | Version: 3.2
(models, ORM) |
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):
* status: new => closed
* resolution: => wontfix
* component: contrib.contenttypes => Database layer (models, ORM)
* type: Bug => New feature
Comment:
`SeparateDatabaseAndState` is ''"a highly specialized operation that lets
you mix and match the database (schema-changing) and state (autodetector-
powering) aspects of operations."'' (see
[https://docs.djangoproject.com/en/3.2/ref/migration-
operations/#django.db.migrations.operations.SeparateDatabaseAndState
docs]). If you want to use it to rename models you need to also update
content types in the `database_operations`. Django will not analyze raw
SQL queries, there is also now way to provide a sensible warning.
--
Ticket URL: <https://code.djangoproject.com/ticket/32787#comment:1>
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/066.dae734cc05325589caa739cac650a37f%40djangoproject.com.
