Migration fails on schema downgrade even for a DropMongoMigrationStrategy()

[MattA48]

Hi,

This may well be WorkingAsIntended but we see the drop migration strategy fail with an InvalidOperationException due to a schema downgrade.

I understand the downgrade issue for true migrations, but isn't this a bit overkill for the Drop strategy? Unless there's concern that there will be a new collection in the new schema that's missed off.

[gottscj]

@MattA48,

I see your point.
I will try to get it done to next release.

Thanks!

[MattA48]

Thanks for that. It's a pain to manually have to delete on testing servers that jump between dev branches

[gottscj]

@MattA48
Should be supported in the latest release. let me know if it works for you. :)

[MattA48]

Thanks - going to be a bit hard to test immediately, as we need a version past this for it to migrate down from, but it'll hopefully avoid this annoying manual deletion step when we do

[gottscj]

sure thing. I will close this, you can open it again if you encounter issues