From be5e3b46f78d54f8fae5dc255295d771c2becaac Mon Sep 17 00:00:00 2001 From: David Sanders Date: Fri, 9 Sep 2022 00:02:58 +1000 Subject: [4.1.x] Fixed #33996 -- Fixed CheckConstraint validation on NULL values. Bug in 667105877e6723c6985399803a364848891513cc. Thanks James Beith for the report. Backport of e14d08cd894e9d91cb5d9f44ba7532c1a223f458 from main --- tests/postgres_tests/test_constraints.py | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) (limited to 'tests/postgres_tests') diff --git a/tests/postgres_tests/test_constraints.py b/tests/postgres_tests/test_constraints.py index 2850d0eb3d..74c07e4fab 100644 --- a/tests/postgres_tests/test_constraints.py +++ b/tests/postgres_tests/test_constraints.py @@ -146,9 +146,7 @@ class SchemaTests(PostgreSQLTestCase): check=Q(ints__startswith__gte=0), name="ints_positive_range", ) - msg = f"Constraint “{constraint.name}” is violated." - with self.assertRaisesMessage(ValidationError, msg): - constraint.validate(RangesModel, RangesModel()) + constraint.validate(RangesModel, RangesModel()) def test_opclass(self): constraint = UniqueConstraint( -- cgit v1.3