p15693087
/
django
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

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.
This commit is contained in:
Michael Manfre 2014-01-08 10:52:13 -05:00
parent f343f5e538
commit 1dbbdb29a0
1 changed files with 9 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
tests/one_to_one_regress/tests.py
View File

@ -1,5 +1,6 @@
from __future__ import unicode_literals from __future__ import unicode_literals
from django.db import connection
from django.test import TestCase from django.test import TestCase
from .models import (Bar, Favorites, HiddenPointer, Place, Restaurant, Target, from .models import (Bar, Favorites, HiddenPointer, Place, Restaurant, Target,
@ -226,6 +227,9 @@ class OneToOneRegressionTests(TestCase):
with self.assertRaises(UndergroundBar.DoesNotExist): with self.assertRaises(UndergroundBar.DoesNotExist):
p.undergroundbar p.undergroundbar
# 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() UndergroundBar.objects.create()
# When there are several instances of the origin # When there are several instances of the origin