It looks like a bug in 2.1.0. For now, you should stick 'gem
"activerecord", "=2.0.2"' at the top of your app :-)

On Thu, Jul 10, 2008 at 5:01 PM, Joshua Miller <[EMAIL PROTECTED]> wrote:
> Hi all,
> I have a little camping micro-blog that's working well with the cookie
> session store, but falls over when I try to use the AR session store.
> The changes I made were:
> require 'camping/session' becomes require 'camping/ar/session'
> module Blog; include Camping::Session; end becomes module Blog;
> include Camping::ARSession; end
> and I did the create_schema in Blog.create.
> It set up the session table correctly, it adds a new row with a
> session id and sets a cookie on the browser correctly, but it never
> saves anything to the session state hash.  Do I need to do something
> differently to make @state save itself?  Using the cookie session
> store, changes are saved anytime I do something to @state, which is
> how I would expect it to work.
> I'm using the latest version from why's git repo with the default sqlite 
> setup.
> Thanks!
> Josh
> _______________________________________________
> Camping-list mailing list

Magnus Holm
Camping-list mailing list
  • AR Sessions Joshua Miller
    • Re: AR Sessions Magnus Holm

Reply via email to