This question is locked. New answers and comments are not allowed.
Last spring, I evaluated OpenAccess ORM for a project I was starting, primarily because I want to be able to make changes in the Microsoft SQL database schema and have them easily carried over to the model.
At the time, I rejected ORM primarily because I encountered so many bugs, but now that ORM has had some time to mature, I'm thinking about converting from Entity Framework 4 to ORM, hoping to get more flexibility to make schema changes as the project progresses.
Does anyone have advice for me? Specifically:
Thanks for the help!
At the time, I rejected ORM primarily because I encountered so many bugs, but now that ORM has had some time to mature, I'm thinking about converting from Entity Framework 4 to ORM, hoping to get more flexibility to make schema changes as the project progresses.
Does anyone have advice for me? Specifically:
- Is it really easier to make schema changes with ORM than with EF? I have each EF model class in a separate file, and it's easier to make changes than I expected, but still has a lot of room for improvement, Also, I remember that ORM didn't seem all that good in propagating changes at the time I evaluated it..
- Is ORM stable now?
- Are there other factors I should consider, favoring either ORM or EF?
Thanks for the help!