Merge lp:~widelands-dev/widelands-website/correct_migration into lp:widelands-website
Proposed by
kaputtnik
Status: | Merged | ||||
---|---|---|---|---|---|
Merged at revision: | 420 | ||||
Proposed branch: | lp:~widelands-dev/widelands-website/correct_migration | ||||
Merge into: | lp:widelands-website | ||||
Diff against target: |
29 lines (+4/-4) 2 files modified
wlmaps/migrations/0001_initial.py (+2/-2) wlmaps/models.py (+2/-2) |
||||
To merge this branch: | bzr merge lp:~widelands-dev/widelands-website/correct_migration | ||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
SirVer | Approve | ||
Review via email: mp+302883@code.launchpad.net |
Description of the change
Correct the disturbing migration for wlmaps.
Since Django uses the migration files to detect changes, it should be save to change both, the model and the migration file.
If you think this is unsafe, we could only change the model, run "makemigrations" and "migrate". But this will make a new migration file which we will have to ship.
I wonder that Django makes migrations for such little changes, which are not relevant for the database. In this case the value for "upload_to" isn't stored in the database at all.
To post a comment you must log in.
lgtm. That change seems safe enough to ship as is.