Mojca Miklavec wrote: > Now I need to test (I have switched to mysql). > > On the server I had a different issue (table created, but application > claimed it was not), so I have switched to mysql on both the local > machine and server.
I had a similar issue, but it turned out that I hadn't run the db migration for the production environment, which is what I was running in. You could solve the issue without switching over to mysql for development by making sure that you're running in the environment you intend. For me, running through apache using phusion passenger, this meant adding a RailsEnv value into the VirtualHost block in the appropriate apache .conf -- Posted via http://www.ruby-forum.com/. -- 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 [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
