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_formsets/tests.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'tests/model_formsets') diff --git a/tests/model_formsets/tests.py b/tests/model_formsets/tests.py index ce6f4ab137..b5e410738e 100644 --- a/tests/model_formsets/tests.py +++ b/tests/model_formsets/tests.py @@ -671,7 +671,7 @@ class ModelFormsetTest(TestCase): self.assertEqual(book1.title, 'Flowers of Evil') self.assertEqual(book1.notes, 'English translation of Les Fleurs du Mal') - @skipUnlessDBFeature('ignores_nulls_in_unique_constraints') + @skipUnlessDBFeature('supports_partially_nullable_unique_constraints') def test_inline_formsets_with_nullable_unique_together(self): # Test inline formsets where the inline-edited object has a # unique_together constraint with a nullable member -- cgit v1.2.1