Opened 9 years ago

Closed 9 years ago

#25983 closed Uncategorized (needsinfo)

annotate migrations with Django version

Reported by: Sergey Fedoseev Owned by: Sergey Fedoseev
Component: Migrations Version: 1.9
Severity: Normal Keywords:
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

As we know different Django versions could create and apply migrations in the different way. It appears that in some cases things could work but state is broken (see #23521). It might be helpful to know what version of Django generated and applied specific migration to understand after a while why things are broken.

I propose to add version info to migration files and table.

Change History (3)

comment:1 by Sergey Fedoseev, 9 years ago

Owner: changed from nobody to Sergey Fedoseev
Status: newassigned

comment:2 by Tim Graham, 9 years ago

As far as the migration files go, is this different from #25259 in Django 1.9?

I think you'll need to expand a bit on the rationale to add a new column to the django_migrations table (and probably propose it on the DevelopersMailingList).

comment:3 by Tim Graham, 9 years ago

Resolution: needsinfo
Status: assignedclosed
Note: See TracTickets for help on using tickets.
Back to Top