#27080: `as_manager` on QuerySet should pass down `use_in_migrations` to new
Manager instance
----------------------------------------------+--------------------
Reporter: leifdenby | Owner: nobody
Type: Bug | Status: new
Component: Database layer (models, ORM) | Version: 1.10
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 1
Easy pickings: 0 | UI/UX: 0
----------------------------------------------+--------------------
When using the convenience method `as_manager` on a QuerySet the attribute
`is_in_migrations`
(https://docs.djangoproject.com/en/1.9/topics/migrations/#model-managers)
is currently not passed down. This means that when creating a migration
the `Manager`s which a created from `QuerySet`s won't be serialised into
the migration. The current workaround would be to create Manager class
from the QuerySet, thereby using the old approach where
`QuerySet.as_manager` isn't used.
--
Ticket URL: <https://code.djangoproject.com/ticket/27080>
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/052.586ddd82e73218f3a4f093287073fee0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
