tropikoder

@hfhbd the error we hit may be caused by views or by foreign keys. could you please run CI on this PR? thanks

> Nice! But could you please add a test? Where could i look in the code base for an example of a test that expects an exception? Thanks

Thanks for the help. You are correct in your suggestions. I asked a colleague who has Android Studio to run the pipeline and his machine gets an out of memory...

Also, there are some things in the tests that i've never used and I didn't find docs for, such as 1.db. I made a new commit that removes it.

Is there a way to build just the jvm jars so i can run my fork locally from my main project (which has the hundreds of migrations and squash problem)?...

Thanks @hfhbd My colleague was able to run the locally installed jars from our fork. It seems that there's a bug when migrations drop views (they get mixed up with...

using the local jars we noticed that the matching of create/drop statements fails when the View drop statement has IF EXISTS

> using the local jars we noticed that the matching of create/drop statements fails when the View drop statement has IF EXISTS Actually there are mismatches even without IF EXISTS

@hfhbd i couldn't make a PR that reproduces the error. We gave up on the automated squash and did it manually.

try cleaning the string first (remove the -) with a regex