On 11/12/07, ara.t.howard <[EMAIL PROTECTED]> wrote: > > hi all- > > upgrading some apps from 1.2.3 -->> 1.2.5 and having all kinds of > issues. lot's of functions have disappeared between versions, for > instance #default_value in the pg connection adapter which breaks > drysql, render_action disappearing (as indicated in past versions of > course) which breaks active scaffold... etc. > > none of this is a big deal or hard to fix, but it did surprise me > given that it's only a minor version number which, in most circles > would allow api additions and fixes, but no deletions or changes to > calling signatures. > > what is the rails' versioning number policy? > > if this is posted somewhere i didn't have success finding it, > apologies in advance. > > cheers. > > a @ http://codeforpeople.com/ > --
Are you sure you are really upgrading to 1.2.5, and not 1.2.5.blah? If you are using RAILS_GEM_VERSION to set your rails version (not vendor/rails), you may actually be using the 2.0 prerelease if you aren't careful. There was a fix that went into 1.2.5 to boot.rb to fix this issue... - Rob --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" 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-core?hl=en -~----------~----~----~----~------~----~------~--~---
