search for: pritzker

I''m at the bloody forehead stage, so I figure it''s time to ask. After installing the robot coop''s memcache-client which everyone apparently recommends, it refuses to work because the rails cache.rb is invoking the read() method on the cache, which it _does not have_. Their library has get() and put() but no read() and write() as rails expects. What gives? Is

I''ve written a plugin to allow for time based fragment caching. It lets you do things like: <% cache ''fragment_name'', 10.minutes.from_now do %> <p>something intensive which will be cached for 10 minutes</p> <% end %> Also, there''s a convenience method so that in your controllers you can do: when_fragment_expired

Here is a discussion of a problem and potential solution for Rails validations. Rails has a fundamental problem with validations in that it essentially requires you to either 1. Accept the default error messages (which can often lead to ugly and unfriendly messages for the user) 2. Override validation messages at the model level like so validates_uniqueness_of :field, :message =>

Hi, When I run rake, everything works fine but when I run rake test:units I get an error apparently while it''s trying to create db tables saying the table already exists. I ran rake with trace to see the differences. It appears that rake test:units does db:schema:load twice, maybe that is the problem? Anyone know why this might be? Output of trace below Rake ** Invoke default