From c3904deb919823af577adf5d9d35e9c113eb8289 Mon Sep 17 00:00:00 2001 From: Aymeric Augustin Date: Sat, 19 Sep 2015 13:36:38 +0200 Subject: Fixed #25160 (again) -- Moved data loss check on reverse relations. Moved data loss check when assigning to a reverse one-to-one relation on an unsaved instance to Model.save(). This is exactly the same change as e4b813c but for reverse relations. --- docs/releases/1.8.5.txt | 4 ++++ docs/releases/1.8.txt | 3 +++ 2 files changed, 7 insertions(+) (limited to 'docs') diff --git a/docs/releases/1.8.5.txt b/docs/releases/1.8.5.txt index 5a19a50137..ce03577cde 100644 --- a/docs/releases/1.8.5.txt +++ b/docs/releases/1.8.5.txt @@ -39,3 +39,7 @@ Bugfixes * Fixed custom queryset chaining with ``values()`` and ``values_list()`` (:ticket:`20625`). + +* Moved the :ref:`unsaved model instance assignment data loss check + ` on reverse relations to ``Model.save()`` + (:ticket:`25160`). diff --git a/docs/releases/1.8.txt b/docs/releases/1.8.txt index a6fa2785fc..a2d98656b6 100644 --- a/docs/releases/1.8.txt +++ b/docs/releases/1.8.txt @@ -702,6 +702,9 @@ Assigning unsaved objects to relations raises an error ... ValueError: save() prohibited to prevent data loss due to unsaved related object 'author'. + A similar check on assignment to reverse one-to-one relations was removed + in Django 1.8.5. + Assigning unsaved objects to a :class:`~django.db.models.ForeignKey`, :class:`~django.contrib.contenttypes.fields.GenericForeignKey`, and :class:`~django.db.models.OneToOneField` now raises a :exc:`ValueError`. -- cgit v1.3