mirrors/django
1
0
Fork 0
mirror of https://github.com/django/django.git synced 2025-10-31 09:41:08 +00:00
Code Issues 32 Releases Wiki Activity

[1.7.x] Fixed #22863: Improve clarity of makemigrations for non-db params

Browse Source
This commit is contained in:
Andrew Godwin
2014-06-19 23:40:59 -07:00
parent 30d8b95139
commit bfe5f72c7e
2 changed files with 7 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docs/topics/migrations.txt
View File

@@ -60,6 +60,12 @@ Migrations will run the same way on the same dataset and produce consistent
results, meaning that what you see in development and staging is, under the
same circumstances, exactly what will happen in production.
Django will make migrations for any change to your models or fields - even
options that don't affect the database - as the only way it can reconstruct
a field correctly is to have all the changes in the history, and you might
need those options in some data migrations later on (for example, if you've
set custom validators).
Backend Support
---------------