ORM or direct SQL?

Possible duplicate:
Using ORM or plain SQL?

Would you decide to use ORM or some kind of house that was spun DAL? And why?

The advantages of ORM seem obvious - better structure / organization, better language, etc. But I'm worried about performance issues. Does anyone have stories about the war? Any ideas about less obvious risks or rewards will be greatly appreciated.

+3
source share
7 answers

I would use ORM precisely for the reasons you mentioned.

. , SQL, , .

+5

, .

, ORM ( L2SQL, Subsonic, EF NHibernate ..), DAL , sprocs.

ORM , , , , ORM, , , ORM - (N + 1 , ..).

+4

( ) ORM , , .

; ORM / , . , .

, , ORM. , LINQ to SQL.

, , DAL , , .

0

, ORM. , SQL , . . , ... ORM , .

, , , SQL, ORM, raw_sql , .

0

, , , , IMHO ORM reaseon, , ( ) bounderies, , Query wethr, SQL HQL ANY_OTHER_SUTFF_QL,

, ORM, , ORM SAVE UPDATE DELETE

0

, - . , , .

, , , .

, , , , , .

0

I think it depends on what project you are working on. If you are programming using some OO language, it might be a good idea to use ORM. But if your project is lower-level or you really care about performance (I believe that a well-designed ORM will not give you poor performance), then direct sql might be the best choice.

0
source

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


All Articles