Replies: 1 comment 6 replies
-
@m4rkyx Hi, thanks for discussing this. Is your proposed pseudo-code:
Separately, it seems CompatiblityMode should be set to STRICT. I don't understand from reading the discussion you linked why the default is LOOSE. That behavior seems chaotic to me. It would be a breaking change, but a sensible one that could avoid disastrous results. @fubar-coder Any idea why we would keep the default to be LOOSE? Am I not thinking of something? |
Beta Was this translation helpful? Give feedback.
6 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello guys,
As we saw here, there is a comptability mode that we can set to STRICT (default is LOOSE) when applying migration.
We're using SQLite and there is some limitations that we need to handle in our migrations.
Currently, FluentMigrator does not apply all of our migrations but doesn't say anything.
So is it possible to stop the migration process when a SQL statement is in error or unhandled by the database provider ?
Thanks a lot :)
PS : The last version of SQLite 3.35.0 support ALTER TABLE DROP COLUMN, are you planning to implement it quickly ?
Beta Was this translation helpful? Give feedback.
All reactions