All geek questions in one place

What are the benefits of connecting to .NET in SQL Server in terms of ORM?

In Java, Hibernate is king in terms of automating code / database synchronization. And I know that NHibernate is the equivalent of .NET, and that LINQ has some cool SQL functions (despite not being developed further than IIRC).

But are there any benefits of pairing .Net development with a SQLServer database? Is the magic of automatically saving objects possible? Or these days, your language / database connection is not much different?

+3
source share
4 answers

A simple .NET connection with SQL will not give you anything good in ORM.

, , , , , .

Linq2Sql, , NHibernate (Hibernate .NET) .

+2

, , .

+2

, , , SQL Server . .net + sql, - . .net + sql - MS, , , , ( ).

ORM , . LINQ2SQL, . , , EF, Subsonic NHibernate.

, / ORM , , - , , - , .

+1

" ORM", , .NET- SQL Server, - Linq to SQL. Linq to SQL , , ORM Visual Studio ( , ...) , , Linq. , , Linq to SQL , -, ORM.

Other benefits are truly specific and not particularly ORM related, such as being better suited to CLR stored procedures available with SQL Server 2005.

0
source

Source: https://habr.com/ru/post/1752831/

More articles:


All Articles