http://blog.maxaller.name ruby, ubuntu, etc Sun, 11 Jul 2010 07:01:36 +0000 http://wordpress.org/?v=2.8.5 en hourly 1 http://blog.maxaller.name/2009/03/gotcha-with-sequel-and-association-caching/ http://blog.maxaller.name/2009/03/gotcha-with-sequel-and-association-caching/#comments Sun, 08 Mar 2009 19:30:06 +0000 Max http://blog.maxaller.name/?p=73 One thing to remember with Sequel is that it caches associations -- for an hour, by default. Normally this is good -- if I say my_model.my_associated_models twice in one request, I'd like that to be cached. But at least with Ramaze, where you can access a variable that persists between requests (via session, like session[:user]), you have to remember that associations on that session object get cached, too. So what does that mean? That means if you have a user view their posts (with session[:user].posts), and then they go make a post, and then they come back to view their posts again...the new post won't be in the list of posts! So you have two basic options here, that I know of -- either a) manually kill the cache by putting session[:user].refresh on the action that alters the associations of session[:user], or b) put session[:user].refresh in a place that gets executed at the beginning of every request.

]]> http://blog.maxaller.name/2009/03/gotcha-with-sequel-and-association-caching/feed/ 0