LINQ has one big advantage over most other data access methods: it focuses around the metaphor “ query expression ”, which means that queries can be passed as objects, modified and modified before they are executed (iterated). In practice, this means that the code can be modular and better isolated. The data access repository will return the "orders" request, then the intermediate filter in the request processing pipeline will decorate this request with a filter, then it will be passed to the display module, which will add sorting and pagination, etc. In the end, when its repetition, the expression completely transformed into a very specificSELECT ... WHERE ... ORDER BY ... LIMIT ...(or another landing page, such as ROW_NUMBER). For application developers, this is priceless and there is simply no viable alternative. That is why I believe LINQ is here to stay and will not disappear after 2 years. This is definitely more than just a fad. And I specifically refer to LINQ as a database access method.
, LINQ . , (XML, , , SQL) , , .Net 4.0, , , LINQ- , LINQ . , , SQL, DBA. .