From cff59bedc23fd4d53557f677ddc42402b56963d0 Mon Sep 17 00:00:00 2001 From: Aymeric Augustin Date: Wed, 7 May 2014 22:03:10 +0200 Subject: Split ignores_nulls_in_unique_constraints feature. Oracle and SQL Server don't have exactly the same limitations. It's worth treating them differently. --- tests/model_forms/tests.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'tests/model_forms') diff --git a/tests/model_forms/tests.py b/tests/model_forms/tests.py index 20bdc2b79e..c3b4c339c0 100644 --- a/tests/model_forms/tests.py +++ b/tests/model_forms/tests.py @@ -650,7 +650,7 @@ class UniqueTest(TestCase): form = TripleForm({'left': '1', 'middle': '3', 'right': '1'}) self.assertTrue(form.is_valid()) - @skipUnlessDBFeature('ignores_nulls_in_unique_constraints') + @skipUnlessDBFeature('supports_nullable_unique_constraints') def test_unique_null(self): title = 'I May Be Wrong But I Doubt It' form = BookForm({'title': title, 'author': self.writer.pk}) -- cgit v1.3