New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Set of down migrations works strange #27

Open

vargur88 opened this issue Mar 2, 2020 · 0 comments

Labels

bug

vargur88 commented Mar 2, 2020 •

edited

Loading

Hi

I'm trying to test the scenario, when i have to do multiple document downgrade migrations, i.e. 1.0.2 -> 1.0.0

Start the app. Up to 1.0.2 (including 1.0.1) - works ok. Close the app.
Start the app. Down to 1.0.1 - works ok. Stop the app.
Start the app. Down to 1.0.0 - calling migration for 1.0.1 version (got exception, because there is no field with renamed at step 2 name)

.netCore, use RuntimeVersion & CollectionLocation attributes together

PS: also why downgrade from 1.0.2 to 1.0.1 doesn't do any down migrations when I try StartUpVersion & CollectionLocation attributes ?

SRoddis added the bug label

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment