.NET Framework 3.5 SP1: LINQ perf improvements (LINQ to Objects and LINQ to SQL)

re: .NET Framework 3.5 SP1: LINQ perf improvements (LINQ to Objects and LINQ to SQL)

Dinesh Kulkarni - MSFT — Wed, 03 Sep 2008 08:45:19 GMT

Mats,

First, my apologies on behalf of the new spam filter. I don't have moderation turned on so I am less punctual about monitoring comments. For some reason that I can't figure out, your comment was flagged as spam and remained unpublished.

As for your suggestion about not retrieving Category, why do you need the "fake" Category object anyway? You can just set Product.CategoryID to 25 if you like. What value does a new'ed up Category provide?

Thanks,

Dinesh

Object Identity tracking changes with LINQ to SQL SP1

Wooley's LINQ Wonderings — Thu, 21 Aug 2008 16:25:29 GMT

When we wrote LINQ in Action, we took a bit of time to explain how the identity tracking system worked

re: .NET Framework 3.5 SP1: LINQ perf improvements (LINQ to Objects and LINQ to SQL)

Mats Helander — Mon, 18 Aug 2008 20:57:40 GMT

Hi Dinesh,

"So an id-based query will not cause a trip to the database."

Excellent! :-) Now the next thing in this vein is to allow me to ask for objects by ID and get them without hitting the database /even when the object is not in the cache/!

For example, I want to create a new Product and set its Category to point to the category with ID 25. To do that I want to ask for the Category object with ID 25 and to get it (without asking the DB) regardless of whether it is in the cache or not. The result should be the same as setting a primitive CategoryID property on the Product to 25. At the end of the operation, only one SQL statement should have been sent to the database: the Insert statement.

/Mats

.NET 3.5 SP1 LINQ improvements

LINQ in Action - LINQ Book & News — Tue, 12 Aug 2008 14:30:47 GMT

In May, I announced the changes related to LINQ that were included in .NET 3.5 Service Pack 1 Beta. Now

.NET 3.5 SP1 LINQ improvements

Fabrice's weblog — Tue, 12 Aug 2008 14:24:21 GMT

In May, I announced the changes related to LINQ that were included in .NET 3.5 Service Pack 1 Beta. Now

Important LINQ Changes in .NET 3.5 SP1

SQLBI - Marco Russo — Tue, 12 Aug 2008 10:50:48 GMT

Dinesh Kulkarni wrote an important post about changes in LINQ introduced by .NET 3.5 SP1 that has been

Important LINQ Changes in .NET 3.5 SP1

Marco Russo — Tue, 12 Aug 2008 10:50:35 GMT

Dinesh Kulkarni wrote an important post about changes in LINQ introduced by .NET 3.5 SP1 that has been