#18782: database "view" treated as "table" on flush (mysql)
-------------------------------------+-------------------------------------
Reporter: rodolfo_3 | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 1.4
(models, ORM) | Resolution:
Severity: Normal | Triage Stage: Accepted
Keywords: mysql introspection | Needs documentation: 0
table view | Patch needs improvement: 0
Has patch: 1 | UI/UX: 0
Needs tests: 0 |
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by akaariai):
I do like the idea of setting automatically managed=False for existing
views. The problem I see with this approach is that this goes somewhat
against the philosophy of Django - we do not alter the models based on
inspection, we trust the models to be correct. So, on that basis a light
-0 on this approach. One of the worries is that we would need to
consistently set the managed flag in app loading, not only in syncdb/flush
etc.
--
Ticket URL: <https://code.djangoproject.com/ticket/18782#comment:5>
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
