fix: invalidate empty-table proof after writes and table renames
This commit is contained in:
1 parent
c7a4376d35
commit
66f39b1c48
7 files changed
+285
-29
No files matched your search
+5
-1
@@ -2,7 +2,11 @@
|
||||
|
||||
Bug:
|
||||
- Do not report a required column added to a table unconditionally created earlier in the same migration.
|
||||
Raw SQL, data migrations, and required columns added to existing tables remain linted.
|
||||
SQL inserts and data operations, including nested `SeparateDatabaseAndState` operations,
|
||||
invalidate that proof. Raw SQL, data migrations, and required columns added to existing tables
|
||||
remain linted; nested data operations receive the same checks as top-level operations. Custom
|
||||
database operations and table renames invalidate the proof unless they are known declarative
|
||||
schema operations.
|
||||
|
||||
## 6.0.0
|
||||
|
||||
|
||||
Reference in new issue
Block a user