#21020: Allow Migrations to use parent classes migration profile -------------------------------------+------------------------------------- Reporter: anonymous | Owner: nobody Type: New feature | Status: closed Component: Database layer | Version: master (models, ORM) | Resolution: invalid Severity: Normal | Triage Stage: Keywords: | Unreviewed Has patch: 0 | Needs documentation: 0 Needs tests: 0 | Patch needs improvement: 0 Easy pickings: 0 | UI/UX: 0 -------------------------------------+------------------------------------- Changes (by mjtamlyn):
* status: new => closed * resolution: => invalid Comment: `django.db.migrations` is not just South pulled in. It's actually a rewrite of the entire concept to make it better. Fields now require a `deconstruct` method to be used in migrations. As this is a simple method, it is automatically transferred onto subclasses. See the release notes for the current skeleton docs: https://docs.djangoproject.com/en/dev/releases/1.7/#new-method-on-field- subclasses -- Ticket URL: <https://code.djangoproject.com/ticket/21020#comment:2> 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/067.8ab866484dfbb784eeee7f23590d2e51%40djangoproject.com. For more options, visit https://groups.google.com/groups/opt_out.