fix django 3.2 degradation

tbicr · Apr 27, 2024 · 18d0bff · 18d0bff
1 parent 3209249
commit 18d0bff
Show file tree

Hide file tree

Showing 2 changed files with 11 additions and 0 deletions.
diff --git a/CHANGES.md b/CHANGES.md
@@ -1,5 +1,8 @@
 # django-pg-zero-downtime-migrations changelog
 
+## 0.15
+  - fixed django 3.2 degradation with missing `skip_default_on_alter` method
+
 ## 0.14
   - fixed deferred sql errors
   - added django 5.0 support

diff --git a/django_zero_downtime_migrations/backends/postgres/schema.py b/django_zero_downtime_migrations/backends/postgres/schema.py
@@ -432,6 +432,14 @@ def _add_column_unique(self, model, field):
             self.deferred_sql.append(self._create_unique_sql(model, [field.column]))
         return ""
 
+    if django.VERSION[:2] <= (3, 2):
+        def skip_default_on_alter(self, field):
+            """
+            Some backends don't accept default values for certain columns types
+            (i.e. MySQL longtext and longblob) in the ALTER COLUMN statement.
+            """
+            return False
+
     def column_sql(self, model, field, include_default=False):
         """
         Take a field and return its column definition.