Greg Christopher wrote: > Hi, > > I was wondering if there is a way to skip the application of a > named_scope to calls made in legacy migrations. I am working with some > old migrations that include some data manipulation tasks, and my default > scope is preventing those migrations from running. I'm trying to avoid > editing those migration files with with_exclusive_scope.
Generally speaking, you shouldn't be running very old migrations -- for existing installations, the migrations get run one at a time, and for new installations, you should just use rake db:schema:load . You've found out a reason for this the hard way. :) What exactly are you trying to do? > > Thanks, > > -G Best, -- Marnen Laibow-Koser http://www.marnen.org [email protected] -- 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 -~----------~----~----~----~------~----~------~--~---
