dataContext.storedProcedure(params).Skip(4).Take(3) - where is it executed
-
Hi! let's assume that the sproc returnes 20 rows. well, i know that the sproc is going to be executed on the DB but will Skip and Take do their stuff after the data (20 rows) from the sproc is returned to the application or will linq "do it's magic" and call converted to sql statements Skip and Take on the DB and return only 3 rows to the application? thanks for any help :D
life is study!!!
-
Hi! let's assume that the sproc returnes 20 rows. well, i know that the sproc is going to be executed on the DB but will Skip and Take do their stuff after the data (20 rows) from the sproc is returned to the application or will linq "do it's magic" and call converted to sql statements Skip and Take on the DB and return only 3 rows to the application? thanks for any help :D
life is study!!!
Seishin# wrote:
will linq "do it's magic"
Yes! Exactly! The definition of link in Websters just says "see magic". And if the link magic is not enough it will conjure the C# magic. If that is not enough C# will conjure C++ magic which will conjure C magic if needed which in turn, if needed, will conjure assembly magic. Whew
led mike
-
Seishin# wrote:
will linq "do it's magic"
Yes! Exactly! The definition of link in Websters just says "see magic". And if the link magic is not enough it will conjure the C# magic. If that is not enough C# will conjure C++ magic which will conjure C magic if needed which in turn, if needed, will conjure assembly magic. Whew
led mike
-
Hi! let's assume that the sproc returnes 20 rows. well, i know that the sproc is going to be executed on the DB but will Skip and Take do their stuff after the data (20 rows) from the sproc is returned to the application or will linq "do it's magic" and call converted to sql statements Skip and Take on the DB and return only 3 rows to the application? thanks for any help :D
life is study!!!
Websters also says "post to linq forum" ;P It depends if it's a delayed query or not. If not, then it is done against and in-memory sequence
only two letters away from being an asset
-
Websters also says "post to linq forum" ;P It depends if it's a delayed query or not. If not, then it is done against and in-memory sequence
only two letters away from being an asset