Hey all,
I came across a cache problem in my ASP.NET MVC application while
using dblinq. In short, I had a method accepting a parameter which
would use that parameter in a lambda expression:
public IEnumerable<Message> GetInbox(int userId)
{
return this.DataContext.Messages.Where(m => m.MessageTo == userId);
}
Even when passing different user id's to the method, I would always
get the same (the first result).
(For the complete question, see it on SO:
http://stackoverflow.com/questions/951634/dblinq-cache-problem)
So after reading some stuff on this discussion board, I came across
this post:
http://groups.google.com/group/dblinq/browse_thread/thread/b6a5bd2020c9d48e/8a4d3bc60a6839d0?lnk=gst&q=cache+problem#8a4d3bc60a6839d0
I think I'm seeing the same problem here, especially what Jonathan
Pryor describes here. Something to do with closures / QueryCache.
Now, I did a new checkout of the DbLinq code (I was using one 1 month
old or so) and it seems that my problem is now fixed (as a result of
that discussion?). However, I'd like to have some more details. Is it
indeed fixed? Does this come at a huge performance cost? All I really
like is some more info, since it was a scary bug in my application and
I want to have some reassurance before it goes into production ;-)
Thanks!
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"DbLinq" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/dblinq?hl=en
-~----------~----~----~----~------~----~------~--~---
