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 , 9 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:2 by , 9 years ago
comment:3 by , 9 years ago
| Resolution: | → needsinfo |
|---|---|
| Status: | assigned → closed |
Note:
See TracTickets
for help on using tickets.
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_migrationstable (and probably propose it on the DevelopersMailingList).