Lighthouse has a new layout. Prefer the old one? Return to the old layout, and switch back any time from the link at the top of each page.

runa's latest activity

Wednesday, September 23 2009
2449 ActionController::Flash::InstanceMethods::flash triggers the lazy sessions was updated in Ruby on Rails
  • runa
    runa commented at 2:14 PM

    Maybe we need to lobby a little for this?

Monday, August 03 2009
1812 default_scope can't take procs was updated in Ruby on Rails
  • runa
    runa commented at 9:27 PM

    Brian: could you give me an example? I would love to see a simpler solution!

  • runa
    runa commented at 8:35 PM

    Ok, I screwed the formatting before (no preview button? :)

    Loading development environment (Rails 2.3.2)
    Employer.send(:default_scope){{:conditions => {:id => ...
  • runa
    • Tag changed from 2.3, activerecord, default_scope, enhancement, named_scope, patch, scope, tested to 2.3, activerecord, bug, default_scope, enhancement, named_scope, patch, scope, tested
    by runa at 8:33 PM

    Guys, I'm using the monkeypatch from "March 18th, 2009 @ 03:34 PM" and found the following problem: if you find() and object and include it's relationships, the...

Wednesday, April 08 2009
2449 ActionController::Flash::InstanceMethods::flash triggers the lazy sessions was updated in Ruby on Rails
  • runa
    • Tag set to 2.3.2, flash, lazy, sessions
    by runa at 3:00 PM
Tuesday, April 07 2009
2450 ActionController::Response::set_conditional_cache_control! should set only pr... was created in Ruby on Rails
  • runa
    runa created the ticket at 11:31 PM

    While working in setting up a reverse proxy in front of Rails, I found that ActionController::Response::set_conditional_cache_control! sets the Cache-Control he...

2449 ActionController::Flash::InstanceMethods::flash triggers the lazy sessions was created in Ruby on Rails
  • runa
    runa created the ticket at 11:25 PM

    I've just updated to rails 2.3 and I found that calling flash from the view triggers the lazy sessions. I think this is not the expected behavior.

    See the patch...