Well, it turns out that I had left in app/models a renamed version of the previous Client model file (client--previous.rb) which was throwing things off. After I removed the file all worked as expected.
Thanks all for your help, and sorry for the red herring. Luis On Mar 5, 10:02 am, Shiv N Gautam <s.n.gau...@gmail.com> wrote: > On Thu, Mar 5, 2009 at 9:28 PM, luis <luistav...@yahoo.com> wrote: > > > On Mar 5, 9:00 am, Frederick Cheung <frederick.che...@gmail.com> > > wrote: > > > On 5 Mar 2009, at 14:37, luis wrote: > > > > > This happens when trying to save the Client object, here is the stack > > > > trace > > > > Looks like you still have a validation against name. > > > > Fred > > > That seems to be the case, but why? Why does it happen only with > > cache_classes = true? It seems to me that the cache is not being > > flushed... > > The problem could be that rails caches the model schema when the server > starts. > Try to do a Model.reset_column_information where Model is the name of your > model. > > -- > Shiv > > > > -- > > Dick Cavett - "If your parents never had children, chances are... neither > will you." --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
