I'm not optimistic about LINQ.

The leader said, "This year's LINQ is a hot topic. You can check it out ". The IT industry has a lot of confusions. After reading this, I am not optimistic about LINQ.

Language Integrated Query is a language integrated query technology that Microsoft will introduce in C #3.0. It can contain LINQ-to-SQL, LINQ-to-object, and LINQ-to-XML. Among them, using LINQ-to-SQL as Microsoft's ORM is the most striking. In my opinion, although LINQ-to-object and LINQ-to-XML are good, they have a narrow application scope. Moreover, if you want to use LINQ-to-object three times in an enterprise-level project, it means that the data stream of the system is not properly processed. The following LINQ statements refer to the intention of using the database persistence technology as the LINQ-to-SQL statement.

I. There is no essential difference between LINQ and Castle. activerecord (nhibcord). The codegenerate function is mostly implemented, but the generated objects are too rigid and lack the inheritance of objects. Castle. activerecord evolved from hibernate, making it easier to understand and accept.

2. The Lambda Syntax of LINQ is too obscure,CodePoor readability, not easy to test. The concept of object-oriented is proposed to better solve the problem, rather than complicate the problem. In order to escape SQL, people have produced hql again, and now a lambda is coming.

3. LINQ does not support databases other than Microsoft. Although dblinq is available, Oracle is not supported until now (the version released in October 8), and code must be rewritten if it is supported.

4. There is still no improvement in the processing of highly practical dynamic queries by LINQ. For more information, see Google's "LINQ dynamic" or "LINQ dynamic query"

In summary, I am not optimistic about LINQ.

-------------------------------------------------

For comments with several replies, add the second paragraph of this article at noon on January 1, October 31, and modify the originalArticleLamda is lambda.