[django/django] 5643a3: Fixed #10811 -- Made assigning unsaved objects to ...

2 views
Skip to first unread message

GitHub

unread,
Jun 5, 2014, 1:13:05 PM6/5/14
to django-...@googlegroups.com
Branch: refs/heads/master
Home: https://github.com/django/django
Commit: 5643a3b51be338196d0b292d5626ad43648448d3
https://github.com/django/django/commit/5643a3b51be338196d0b292d5626ad43648448d3
Author: Anubhav Joshi <anubh...@gmail.com>
Date: 2014-06-05 (Thu, 05 Jun 2014)

Changed paths:
M django/contrib/contenttypes/fields.py
M django/db/models/fields/related.py
M docs/releases/1.8.txt
M docs/topics/db/examples/many_to_one.txt
M docs/topics/db/examples/one_to_one.txt
M tests/admin_util/tests.py
M tests/contenttypes_tests/tests.py
M tests/many_to_one_regress/tests.py
M tests/multiple_database/tests.py
M tests/one_to_one/models.py
M tests/one_to_one/tests.py
M tests/one_to_one_regress/tests.py

Log Message:
-----------
Fixed #10811 -- Made assigning unsaved objects to FK, O2O, and GFK raise ValueError.

This prevents silent data loss.

Thanks Aymeric Augustin for the initial patch and Loic Bistuer for the review.


Reply all
Reply to author
Forward
0 new messages