Fix #209 - Raise when getting SQL statements fail.

CHANGELOG.md

@@ -1,5 +1,9 @@
-## 4.1.1 (unreleased)
+## 5.0.0 (unreleased)
 
+- **Breaking change**: stop silently ignoring when the internal `sqlmigrate` call fails and the linter cannot analyse the migration.
+Instead, the linter crashes and lets the `sqlmigrate` error raise, in order to avoid letting a problematic migration pass.
+One common reason for such an error is the SQL generation which requires the database to be actually migrated in order to fetch actual constraint names from it.
+The crash is a sign to double-check the migration. But if you are certain the migration is safe, you can ignore it (issue #209)
 - Fixed `RunPython` model import check when using a `through` object like `MyModel.many_to_many.through.objects.filter(...)` (issue #218)
 
 ## 4.1.0