Update for changes to CheckConstraint API

The check parameter is now called condition

Author: jgraham

server/reportmanager/migrations/0001_initial.py

@@ -341,7 +341,7 @@ class Migration(migrations.Migration):
         migrations.AddConstraint(
             model_name="bucketcolor",
             constraint=models.CheckConstraint(
-                check=models.Q(("value__gte", 0), ("value__lte", 16777215)),
+                condition=models.Q(("value__gte", 0), ("value__lte", 16777215)),
                 name="value_range",
             ),
         ),
@@ -372,7 +372,7 @@ class Migration(migrations.Migration):
         migrations.AddConstraint(
             model_name="bucket",
             constraint=models.CheckConstraint(
-                check=models.Q(("priority__gte", -2), ("priority__lte", 2)),
+                condition=models.Q(("priority__gte", -2), ("priority__lte", 2)),
                 name="priority_range",
             ),
         ),

server/reportmanager/models.py

@@ -74,7 +74,7 @@ class Bucket(models.Model):
     class Meta:
         constraints = (
             models.CheckConstraint(
-                check=models.Q(priority__gte=-2) & models.Q(priority__lte=2),
+                condition=models.Q(priority__gte=-2) & models.Q(priority__lte=2),
                 name="priority_range",
             ),
         )
@@ -303,7 +303,7 @@ class BucketColor(models.Model):
     class Meta:
         constraints = (
             models.CheckConstraint(
-                check=models.Q(value__gte=0) & models.Q(value__lte=0xFFFFFF),
+                condition=models.Q(value__gte=0) & models.Q(value__lte=0xFFFFFF),
                 name="value_range",
             ),
         )