summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorDaniel Pyrathon <pirosb3@gmail.com>2014-03-10 15:17:57 +0000
committerMarc Tamlyn <marc.tamlyn@gmail.com>2014-03-10 15:25:18 +0000
commit819e09b848e4f1cc45165a99ffbef1307b215a08 (patch)
treeb424ef7353b1cdaeb60adf166606bc05357b3acc /docs
parent3bd45ba00d0f43e9ea192eca132624b30cae4eee (diff)
Fixed #22210 -- Saving model instances to non-related fields.
Previously, saving a model instance to a non-related field (in particular a FloatField) would silently convert the model to an Integer (the pk) and save it. This is undesirable behaviour, and likely to cause confusion so the validatio has been hardened. Thanks to @PirosB3 for the patch and @jarshwah for the review.
Diffstat (limited to 'docs')
-rw-r--r--docs/releases/1.7.txt4
1 files changed, 4 insertions, 0 deletions
diff --git a/docs/releases/1.7.txt b/docs/releases/1.7.txt
index 52007c98aa..2dd3931060 100644
--- a/docs/releases/1.7.txt
+++ b/docs/releases/1.7.txt
@@ -674,6 +674,10 @@ Models
the new :attr:`ManyToManyField.through_fields <django.db.models.ManyToManyField.through_fields>`
argument.
+* Assigning a model instance to a non-relation field will now throw an error.
+ Previously this used to work if the field accepted integers as input as it
+ took the primary key.
+
Signals
^^^^^^^