#33168: Meta.managed=False field not respected by makemigrations
-------------------------------------+-------------------------------------
Reporter: Javier Domingo | Owner: nobody
Cansino |
Type: | Status: closed
Cleanup/optimization |
Component: Documentation | Version: 3.2
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
* type: Uncategorized => Cleanup/optimization
* resolution: => wontfix
Comment:
I appreciate you'd like to reopen the ticket, however I don't think that
an extra clarification is needed. It's already documented that:
> ''If False, **no database table creation, modification, or deletion
operations will be performed** for this model. This is useful if the model
represents an existing table or a database view that has been created by
some other means. **This is the only difference when managed=False. All
other aspects of model handling are exactly the same as normal.**''
We cannot document here all aspects of model handling.
--
Ticket URL: <https://code.djangoproject.com/ticket/33168#comment:6>
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/064.e4ca3b2cdf3983a0a847dac519dd31f2%40djangoproject.com.
