From 1dbbdb29a040106f072a4a0315a066a251cc4939 Mon Sep 17 00:00:00 2001 From: Michael Manfre Date: Wed, 8 Jan 2014 10:52:13 -0500 Subject: [PATCH] Fixed #21746 - Fixed test_get_reverse_on_unsaved_object test. Test will no longer attempt to insert multiple NULL rows in to a unique field if the database doesn't support it. --- tests/one_to_one_regress/tests.py | 14 +++++++++----- 1 file changed, 9 insertions(+), 5 deletions(-) diff --git a/tests/one_to_one_regress/tests.py b/tests/one_to_one_regress/tests.py index da4309e821..17528de311 100644 --- a/tests/one_to_one_regress/tests.py +++ b/tests/one_to_one_regress/tests.py @@ -1,5 +1,6 @@ from __future__ import unicode_literals +from django.db import connection from django.test import TestCase from .models import (Bar, Favorites, HiddenPointer, Place, Restaurant, Target, @@ -226,12 +227,15 @@ class OneToOneRegressionTests(TestCase): with self.assertRaises(UndergroundBar.DoesNotExist): p.undergroundbar - UndergroundBar.objects.create() + # Several instances of the origin are only possible if database allows + # inserting multiple NULL rows for a unique constraint + if connection.features.ignores_nulls_in_unique_constraints: + UndergroundBar.objects.create() - # When there are several instances of the origin - with self.assertNumQueries(0): - with self.assertRaises(UndergroundBar.DoesNotExist): - p.undergroundbar + # When there are several instances of the origin + with self.assertNumQueries(0): + with self.assertRaises(UndergroundBar.DoesNotExist): + p.undergroundbar def test_set_reverse_on_unsaved_object(self): """