LINQ to Entity : Supported and Unsupported Methods

LINQ to Entity : Supported and Unsupported Methods

  • Comments 5

There is a correction for this Post, so do I have changed the title. Thanks to Chris Love who pointed me the faults with earlier post,

I got few question on some of the popular paging methods of LINQ which does not work on LINQ to Entity. This is by design and quite logical. In LINQ to SQL scenario they do translate to native TSQL and uses some of its properties and functions. Thus this cannot be made generic for other databases like Oracle/DB2.

 

There is a list published in MSDN with the operators at,

 

Projection and Restriction Methods (LINQ to Entities)

Lists the supported and unsupported projection and restriction methods.

 

Join Methods (LINQ to Entities)

Lists the supported and unsupported joining methods.

 

Set Methods (LINQ to Entities)

Lists the supported and unsupported set methods.

 

Ordering Methods (LINQ to Entities)

Lists the supported and unsupported ordering methods.

 

Grouping Methods (LINQ to Entities)

Lists the supported and unsupported grouping methods.

 

Aggregate Methods (LINQ to Entities)

Lists the supported and unsupported aggregating methods.

 

Type Methods (LINQ to Entities)

Lists the supported and unsupported type methods.

 

Paging Methods (LINQ to Entities)

Lists the supported and unsupported paging methods.

 

 

Namoskar!!!

Leave a Comment
  • Please add 6 and 4 and type the answer here:
  • Post
  • PingBack from http://www.codedstyle.com/linq-to-entity-skip-and-take-method-does-not-work/

  • Wriju,

    Is it possible to use row numbers as column in the query and then select the rows based on the row number? Let's say between 0 and 10?

    Thank you!

  • These operators have worked just fine for me with Linq to Entities.?????

  • > In LINQ to SQL scenario they do translate to native TSQL and uses some of its properties and functions. Thus this cannot be made generic for other databases like Oracle/DB2.

    Can you really not figure out how to pass two integers to the EF providers? If EF Providers cannot parse expression trees like LINQ providers, can't you at least send them as additional arguments?

    Every time I think I've seen the worst of it, you guys show me yet another reason why EF is garbage.

    Can you honestly say there is any reason to use EF?

  • @Chris,

    Thanks for pointing it out. I have changed my post.

    Wriju

Page 1 of 1 (5 items)