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

Update README and CHANGELOG

Browse Source
This commit is contained in:
David Wobrock committed 2019-07-30 10:47:20 +02:00
1 parent a74a7497ad
commit c57d3c9286
2 files changed
+4
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

CHANGELOG.md
+3
View File
@@ -3,6 +3,9 @@
* Add `--exclude-migration-tests` option to ignore backward incompatible migration tests. * Add `--exclude-migration-tests` option to ignore backward incompatible migration tests.
* Do not falsely detect dropping `NOT NULL` constraint. * Do not falsely detect dropping `NOT NULL` constraint.
* Detect `DROP TABLE` backward incompatible migration. * Detect `DROP TABLE` backward incompatible migration.
* Detect adding a `UNIQUE` constraint as backward incompatible migration.
* Handle when Django tries to generate the SQL of a migration but raises an exception because
it cannot find the name of a certain constraint (because it has been dropped already).
Internal change: Internal change:
README.rst
+1
View File
@@ -81,6 +81,7 @@ The linter analyses your migrations and checks the SQL for:
- Renaming columns - Renaming columns
- Renaming tables - Renaming tables
- Altering columns (which can be backward compatible and potentially ignored) - Altering columns (which can be backward compatible and potentially ignored)
- Adding a unique constraint
Those are the most important and frequent backward incompatible migrations. Those are the most important and frequent backward incompatible migrations.
We are happy to add more if you can specify them to us. We are happy to add more if you can specify them to us.