![]() ![]() But usually, when we using these tools we use just a small subset of the ORM framework, in most cases, we even don’t know what is most of the features of the big ORMs. If we take any of the existing ORM tools, we will find hundreds of features, which developers of these ORMs are developed during years of their existence. In fact, there are only two benefits of Micro ORM comparing to ORM, the first is simplicity and the second is a great performance. It’s not a huge limitation, but have another tool to keep track of changes to your database will require additional efforts, FluentMigrator doing this job pretty well if you need such a tool. Migration: most of ORM tools support some kind of migration or code first approach, where you design your model and after executing application database objects created based on the model, and when you make changes database updates as well, this feature is not supported by Micro ORM, you have to use 3rd party tools to do a migration.In fact, it’s not a big limitation at all, for example, NHibernate does not have a designer as well (at least a free designer), but it’s extremely easy to set up your model and mapping. No designer: most existing ORM usually have nice designer, where you can create your model, set relationship between objects (a good example Entity Framework), micro ORM does not support it, you should code all your models and relationship. ![]() For me, this was one of the reasons switching from Micro ORM tools This limitation is very annoying, you can still load parent/child object, but you have to construct your SQL query special way or do multiple queries, also when saving parent, you should not forget about children.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |