Actually I didn't have many problems with Rails (if a remember well), just with some methods, like link_to, response_to, etc and many warnings, they were catched doing tests. The files into config directory are very different between RoR v1.2.3 and v3.0.0, it was using fastcgi and the pagination was removed from the core. I had more problems with javascripts because the prototype.js changed and the app had many dependencies with that (in helpers, views) and it was hard to test them. I think you will be alright, because the code should be supported and you have to monitor the log entries looking for errors and warnings.
On May 3, 4:58 am, Hans <[email protected]> wrote: > > A drawback with your approach is that there are many depedents between > models and controllers in my application and > these could be hard to manage in a syepwise process. Exequiel, did you > have any problems with that ??? > -- 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.
