No, quite the opposite. The data already exists in the database and its using standard database functionality to extract only the data that matches the filter. The alternative would be to bring the one million rows back to the client and filter them there which would be a nightmare scenario in terms of network traffic and client processing required
Regards
Richard Blewett - DevelopMentor
http://www.dotnetconsult.co.uk/weblog http://www.dotnetconsult.co.uk
nntp://news.microsoft.com/microsoft.public.dotnet.languages.csharp/<38**********************************@microsoft.co m>
Won't that be a performance hit for large amount of data. What if the
Customers table contains one million rows, these have to be sent over the
network and after the filtering is done it may onlybe 50 rows left that are
any use.
"Richard Blewett [DevelopMentor]" wrote:
The filtering is performed on the server in this case
Regards
Richard Blewett - DevelopMentor
http://www.dotnetconsult.co.uk/weblog
http://www.dotnetconsult.co.uk
Hi
Have a question about DLinq.
The example code floating around looks like this:
Northwind db = new Northwind(@"C:\...\northwnd.mdf");
var custs = from c in db.Customers where c.City == "London" select c;
How does this work. Will it retreive all the rows from the Customer table
and then filter and select. Or does it generate a sql on the fly which will
return only the proper rows.
Or am I getting it all wrong.
[microsoft.public.dotnet.languages.csharp]