ansaurus

Question

Linq-to-sql Compiled Query returns object NOT belonging to submitted DataContext ?

Answer 1

A:

You can try setting the ObjectTrackingEnabled of the context to false. This helped me in this same situation but I later turn it on while updating and inserting records.

DBDataContext.ObjectTrackingEnabled = false; // Read Only

JeremySpouken 2010-03-18 20:36:47

Thanks, I was playing with this before and I was always getting “Data context options cannot be modified after results have been returned from a query..”Anyway this query is used in multiple places in relation with other queries (for selecting or updating) and therefore I would be afraid to set tracking off.

Vladimir Kojic 2010-03-18 21:03:42

Answer 2

A:

It is a bug and it will not be fixed.

Similar problem was described in the post from link below. I tried not to use PK in compiled query as suggested but got the same problem. So there is an issue with compiled queries bypassing the cache.

http://stackoverflow.com/questions/1427624/workaround-for-linq-to-sql-entity-identity-caching-and-compiled-query-bug

Vladimir Kojic 2010-03-22 20:53:51

Answer 3

A:

LINQ to SQL CompiledQuery is good option, but thing that needs to be taken into consideration while using the same is that first time when it is called it takes more time than a routine query would take. Refer to below link...

http://www.a2zmenu.com/LINQ/LINQ%20to%20SQL%20CompiledQuery.aspx

Experts Comment 2010-09-11 14:18:00

ansaurus

tags:

views:

answers:

Linq-to-sql Compiled Query returns object NOT belonging to submitted DataContext ?

related questions