简体繁体 English

数据库优先ORM

[英]Database first ORM

原文 2019-02-21 23:01:32 2 1 wpf/ entity-framework/ mvvm/ nhibernate/ fluent-nhibernate

I am currently about to start out on a project to convert a legacy access front end application using MSSQL backend database to WPF using the MVVM pattern. 我目前正在开始一个项目，以使用MVVM模式将使用MSSQL后端数据库的旧式访问前端应用程序转换为WPF。

The database has around 300 tables so it will need to use and ORM tool to generate the POCO classes using database first driven design. 该数据库大约有300个表，因此需要使用ORM工具通过数据库优先驱动的设计来生成POCO类。

I have recently receiving some mentoring for the project and nHibernate has been recommended as the ORM over Entity. 我最近收到了有关该项目的一些指导，并且已推荐nHibernate作为实体上的ORM。

Looking to find out your recommendations and whether we should be looking to Entity or another ORM as opposed to what is possibly just the one that the mentor has experience using? 希望找到您的建议，我们是否应该寻找实体或另一个ORM，而不是导师有经验的对象？

Thanks in advance, 提前致谢，

1 个解决方案

I'm using NHibernate everywhere. 我到处都在使用NHibernate。 On .NET Core, on .NET Framework, since 2009. Only some projects that are not permitted use of NH i've used EF or other orm or some like this (Linq for SQL or DAAB stuff). 自2009年以来在.NET Core和.NET Framework上运行。只有某些不允许使用NH的项目，我才使用EF或其他orm或类似的东西（用于SQL或DAAB的Linq）。

NHibernate provide more control, more configuration spots and more features instead EF. NHibernate代替EF提供了更多的控制，更多的配置点和更多功能。 It's my recomendation in all scenarios that be use a ORM. 在所有使用ORM的情况下，这都是我的建议。 Dapper solve some questions too. Dapper也解决了一些问题。 But if i have NH i don't need Dapper because we have some types of operate with database. 但是，如果我有NH，则不需要Dapper，因为我们对数据库进行了某些类型的操作。

More options, more responsability. 更多选择，更多责任。 NHibernate is more complex. NHibernate更复杂。 Needs a deep drive into your complexity to understand how give best performance and approach to solve any kind of database interaction. 需要深入了解您的复杂性，以了解如何提供最佳性能和方法来解决任何类型的数据库交互。 Do you do more, but you must know to do. 您是否做得更多，但是您必须知道要做。