Skip to content
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

Come up with a non-EF strategy for handling migrations #11

Open
PorterK opened this issue May 12, 2019 · 0 comments
Open

Come up with a non-EF strategy for handling migrations #11

PorterK opened this issue May 12, 2019 · 0 comments
Assignees
@PorterK
Labels
core feature Features core to the API internal Issues the internal team must work on / discuss low priority
Milestone
MVP

Comments

@PorterK
Copy link
Contributor

PorterK commented May 12, 2019

Need a way to handle migrations without relying on EF (or any other data layer framework) to handle them.

.NET is notorious for suggesting different ORM/data layer tools fairly often, I would like to decouple seeding / migrations from the application itself (seeds / table creation is already done in this way)
@PorterK PorterK added internal Issues the internal team must work on / discuss core feature Features core to the API labels May 12, 2019
@PorterK PorterK added this to the MVP milestone May 12, 2019
@PorterK PorterK self-assigned this May 12, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@PorterK PorterK

Labels
core feature Features core to the API internal Issues the internal team must work on / discuss low priority
Projects
None yet
Milestone
MVP
Development

No branches or pull requests
1 participant
@PorterK