search for: matchcontrols

Hi, I''ve got a table with an inserted_at column. When I insert a record it automatically injects the current date/time, all is well. Then when I insert a second record, it uses the exact same timestamp that is used in the first record. This behavior only seems to occur in production mode. When I restart the server, the problem goes away but then immidetatly occurs again on the

I fired up the debugger and watched the code happen tonight. The problem occurs if the config.action_controller.perform_caching = true in your environment. It''s not set to true in development but it is set to true in production and staging. The problem occurs not in my controllers but in sweeping.rb (part of rails). Rails calls this code for every controller which was instantiated in

Hello R gurus, I have a data set from which i have to extract the gender and age matched rows from controls and disease group disease<-paste(rep(c('y','n'),11)) gender<-paste(rep(c('m','f'),11)) mcp<-rnorm(700,1400) age<-rnorm(32,34) dat<-data.frame(disease=disease,sex=gender,Dr_age=age[1:22],MCP=mcp[1:22]) I have other categorical variables also to