Closed Kronos11 closed 4 years ago
Yeap, agree !!
We have this on our roadmap, but this time we are so busy :( A PR is welcome if you want, if not we try to do a soon as posible!
I'm willing to take a crack at this tomorrow I have some time. What is the general approach you were thinking? Create different projects for the different db providers? and have separate migrations for each? I see need to have a script that would handle the migrations in that case.
Maybe allow the user to setup their own Factory to create the DbContext and allow them to put whatever they want as an options builder? Seems like this is more flexible, but there might be some other issues I'm not aware of?
Well, the aproach could be some like
Look ok?
Sounds good, opened #139
Merged on master, now as 4.0 working version!
It would be extremely helpful if all of the Entity Store logic was separated out and one could simply add in the Entity Framework provider of your choice, for example npgsql or a mysql provider. This would allow me to use the UI without any work whatsoever.