public/django-migration-linter
15
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix typo

Browse Source
This commit is contained in:
Kevin Wu authored and David Wobrock committed 2025-03-30 17:53:05 +02:00
1 parent 76525e47f8
commit c98d2e2183
1 file changed
+1 -1
Download Patch File Download Diff File Expand all files Collapse all files
docs/incompatibilities.md
+1 -1
View File
@@ -113,7 +113,7 @@ Deletion operations often lead to errors during deployment.
:white_check_mark: **Solutions**: :white_check_mark: **Solutions**:
- Deprecate the column before dropping it using [django-deprecate-fields](https://github.com/3YOURMIND/django-deprecate-fields/). - Deprecate the column before dropping it using [django-deprecate-fields](https://github.com/3YOURMIND/django-deprecate-fields/).
This process requires to first make sure that the field is unused (for which `django-deprecate-fields` is made for). This process requires to first make sure that the field is unused (for which `django-deprecate-fields` is made for).
Once the column is unsed, drop it in a migration. This migration will require to be ignored through the [IgnoreMigration](/docs/usage.md#ignoring-migrations) for instance. Once the column is unused, drop it in a migration. This migration will require to be ignored through the [IgnoreMigration](/docs/usage.md#ignoring-migrations) for instance.
- Don't actually drop the column, but fake the drop migration until you are sure you won't roll back. - Don't actually drop the column, but fake the drop migration until you are sure you won't roll back.
Be careful :warning: fake dropping a non-nullable column without a database default will create errors once the code is not aware of the column anymore. Be careful :warning: fake dropping a non-nullable column without a database default will create errors once the code is not aware of the column anymore.