All geek questions in one place

Are there any parts of LINQ that I should avoid for SQL 2000?

I have a SQL 2000 database. SQL 2000 does not support Entity Framework v2. I would like to use LINQ to manage collections in memory.

Assuming I'm not using Entity Framework v2, are there any parts of LINQ in .NET 4 that don't work with SQL 2000? Are TableAdapters doing CRUD operations to use?

As far as I know, using the Entity framework requires explicitly adding the * .edmx file. Therefore, adding *.dmbl (linq to sql) or DataSet (*.xsd) not a problem. It's right? In other words, any LINQ function generates incompatible code, for example. objects?

+6
source share
1 answer

There are some limitations with using Skip and Take in linq2Sql with SQL 2000.

MSDN:

You must use identification elements (IsPrimaryKey) when you use the Take or skip SQL Server 2000 database. The query must be against a single table (that is, not a join) or must be Separate except, cross or union, and should not include the Concat operation . For more information, see "SQL Server 2000" in the standard translation of query statements (LINQ to SQL).

This requirement does not apply to SQL Server 2005.

For more information about unsupported features, see the "SQL Server 2000 Support" section at http://msdn.microsoft.com/en-us/library/bb399342.aspx

+4
source

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

More articles:


All Articles