On Mon, 2006-02-20 at 00:14 -0600, Rick Olson wrote: > > But, this doesn't catch everything (the before_save example is unhelped, > > e.g.). > > Ultimately, the developer can't (and shouldn't have to) predict what the > > future > > is going to bring, and shouldn't have to code around this sort of problem. > > To work around this, I just started creating temporary models per > migration. I find that much nicer than reverting to > ActiveRecord::Base.connection for my delicate sql needs.
> Take a look: http://techno-weenie.net/svn/projects/mephisto/trunk/db/migrate/ FWIW, I also used this technique for Typo's migrations. It works really well. http://www.typosphere.org/trac/ticket/680 (I got bogged down with some odd typoisms around the teens... I'll clean it up and hopefully merge it this week). _______________________________________________ Rails-core mailing list [email protected] http://lists.rubyonrails.org/mailman/listinfo/rails-core
