#23644: Django 1.7: adding order_by to model Meta class causes Django to create
a
meaningless migration
--------------------------------------+------------------------
Reporter: robvdl | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Migrations | Version: 1.7
Severity: Normal | Keywords: migrations
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------
When you add a Meta class with just an order_by to an existing model,
Django 1.7 thinks it needs to create a migration for this change, while
this does not change the schema at all and probably shouldn't really
require a migration.
South would not create a migration in this case I am pretty sure, it seems
Django 1.7 does.
--
Ticket URL: <https://code.djangoproject.com/ticket/23644>
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/049.cb925474529c8b076169408009436cd2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
