I have a site that uses MySQL, Rails 1.2.3, and apache (proxy load
balancer). I have 4 mongrels running.
Every so often when I use capistrano to deploy my latest stuff, it
seems that one or more of the rails gets into a “i don’t want to set
created_at” mood. I end up with a sprinkling of records in my db with
created_at of null and some created right around the same time with it
set correctly. If is restart the rails the problem will clear. It
has happened a couple of times. Now I’m getting psychotic and running
sql commands all the time checking the hot tables for the rogue
Anybody else run into this problem? I have since put in a MySQL
constraint to force a non-null created_at but the whole thing makes me
a little nervous about my up to know trusted rails.