Linq-to-sql Compiled Query is caching result from disposed DataContext

Posted by Vladimir Kojic on Stack Overflow See other posts from Stack Overflow or by Vladimir Kojic
Published on 2010-03-18T19:31:02Z Indexed on 2010/03/18 19:41 UTC
Read the original article Hit count: 485

Filed under:

linq-to-sql

Compiled query:

public static Func<OperationalDataContext, short, Machine>
    QueryMachineById = 
       CompiledQuery.Compile((OperationalDataContext db, short machineID) =>
         db.Machines.Where(m => m.MachineID == machineID).SingleOrDefault());

It looks like compiled query is caching Machine object and returning the same object even if query is called from new DataContext (I’m disposing DataContext in the service but I’m getting Machine from previous DataContext).

I use POCOs and XML mapping.

Getting cached object from the same datacontext is ok, but when I call query with new DataContext I don’t want to get object from old datacontext.

Is there something that I don’t do right ?

Thanks, Vladimir

Related posts about linq-to-sql

how can i page my linq to sql result set

as seen on Stack Overflow - Search for 'Stack Overflow'
Remembering MySQL could use the instruction "limit" to indicate where I was starting my result set and how many wanted to have included. Select * FROM Users Limit [start], [Length] How can I do this in LinqToSql >>> More
LINQ to SQL and missing Many to Many EntityRefs

as seen on West-Wind - Search for 'West-Wind'
Ran into an odd behavior today with a many to many mapping of one of my tables in LINQ to SQL. Many to many mappings aren’t transparent in LINQ to SQL and it maps the link table the same way the SQL schema has it when creating one. In other words LINQ to SQL isn’t smart about many to many mappings… >>> More
Comparing LINQ to SQL vs the classic SqlCommand

as seen on Dot net Slackers - Search for 'Dot net Slackers'
tweetmeme_url = 'http://alpascual.com/blog/comparing-linq-to-sql-vs-the-classic-sqlcommand/';tweetmeme_source = 'alpascual';When you are coming from using SqlCommand and SqlConnection is difficult to move to another library for your database needs. For those people still in the limbo to make the decision… >>> More
Comparing LINQ to SQL vs the classic SqlCommand

as seen on Dot net Slackers - Search for 'Dot net Slackers'
tweetmeme_url = 'http://alpascual.com/blog/comparing-linq-to-sql-vs-the-classic-sqlcommand/';tweetmeme_source = 'alpascual';When you are coming from using SqlCommand and SqlConnection is difficult to move to another library for your database needs. For those people still in the limbo to make the decision… >>> More
LINQ to SQL Profiler

as seen on Dot net Slackers - Search for 'Dot net Slackers'
In this article we will be taking a look at the new LINQ to SQL Profiler from HibernatingRhinos. This tool gives you a view into the goings on of LINQ to SQL. Not only does it allow you to see the SQL that is generated by your LINQ queries but it also shows you information about your connections… >>> More

Developer IT

Linq-to-sql Compiled Query is caching result from disposed DataContext - Developer IT

Linq-to-sql Compiled Query is caching result from disposed DataContext

linq-to-sql

Related posts about linq-to-sql

how can i page my linq to sql result set

LINQ to SQL and missing Many to Many EntityRefs

Comparing LINQ to SQL vs the classic SqlCommand

Comparing LINQ to SQL vs the classic SqlCommand

LINQ to SQL Profiler

Categories cloud