Avoiding Linq real database operations

Question

If I implement this interface:

public interface IProductsRepository
{
    IQueryable<Product> Products { get; }
}

... using Linq to SQL

Will this produce real database queries?

var x = from p in repositoryInstance.Products where price > 100;

If so how can I avoid callers from executing complex and slow sql statements?

Stephen Cleary · Accepted Answer · 2011-02-02 01:36:10Z

3

LINQ to SQL (and other LINQ providers) will not allow invalid SQL statements. If possible, a compile-time error will prevent the code from compiling. If that's not possible, an error will be thrown at runtime.

answered Feb 2, 2011 at 1:36

Stephen Cleary

460k78 gold badges721 silver badges858 bronze badges

Sign up to request clarification or add additional context in comments.

3 Comments

Eduardo Over a year ago

Hi. I mean complex and slow statements.

Eric Petroelje Over a year ago

@Eduardo - you can't really, but there's nothing to stop you from writing a really complex and slow SQL statement either.

Stephen Cleary Over a year ago

@Eduardo: As Eric stated, LINQ will allow complex and slow SQL statements, just like SQL will. One disadvantage to LINQ is that the queries aren't known ahead of time, so some DB optimizations aren't possible. General optimizations are automatic: LINQ will optimize the queries, and then SQL Server will optimize the queries.

Collectives™ on Stack Overflow

Avoiding Linq real database operations

1 Answer 1

3 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

3 Comments

Your Answer

Sign up or log in

Post as a guest

Related