summaryrefslogtreecommitdiff
path: root/docs/build/unreleased/884.rst
diff options
context:
space:
mode:
Diffstat (limited to 'docs/build/unreleased/884.rst')
-rw-r--r--docs/build/unreleased/884.rst24
1 files changed, 24 insertions, 0 deletions
diff --git a/docs/build/unreleased/884.rst b/docs/build/unreleased/884.rst
new file mode 100644
index 0000000..d357d99
--- /dev/null
+++ b/docs/build/unreleased/884.rst
@@ -0,0 +1,24 @@
+.. change::
+ :tags: usecase, batch
+ :tickets: 884
+
+ Named CHECK constraints are now supported by batch mode, and will
+ automatically be part of the recreated table assuming they are named. They
+ also can be explicitly dropped using ``op.drop_constraint()``. For
+ "unnamed" CHECK constraints, these are still skipped as they cannot be
+ distinguished from the CHECK constraints that are generated by the
+ ``Boolean`` and ``Enum`` datatypes.
+
+ Note that this change may require adjustments to migrations that drop or
+ rename columns which feature an associated named check constraint, such
+ that an additional ``op.drop_constraint()`` directive should be added for
+ that named constraint as there will no longer be an associated column
+ for it; for the ``Boolean`` and ``Enum`` datatypes, an ``existing_type``
+ keyword may be passed to ``BatchOperations.drop_constraint`` as well.
+
+ .. seealso::
+
+ :ref:`batch_schematype_constraints`
+
+ :ref:`batch_check_constraints`
+