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

Fixed #24447 -- Made migrations add FK constraints for existing columns

Browse Source 
When altering from e.g. an IntegerField to a ForeignKey, Django didn't
add a constraint.
This commit is contained in:
Jean-Louis Fuchs
2015-03-05 13:41:15 +01:00
committed by Markus Holtermann
parent c36b60836b
commit f4f0060fea
3 changed files with 44 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
django/db/backends/base/schema.py
View File

@@ -709,9 +709,9 @@ class BaseDatabaseSchemaEditor(object):
}
)
# Does it have a foreign key?
if new_field.rel and \
(fks_dropped or (old_field.rel and not old_field.db_constraint)) and \
new_field.db_constraint:
if (new_field.rel and
(fks_dropped or not old_field.rel or not old_field.db_constraint) and
new_field.db_constraint):
self.execute(self._create_fk_sql(model, new_field, "_fk_%(to_table)s_%(to_column)s"))
# Rebuild FKs that pointed to us if we previously had to drop them
if old_field.primary_key and new_field.primary_key and old_type != new_type: