* Rick Olson ([EMAIL PROTECTED]) [060220 01:15]: > 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. It might be > best to create the temporary model classes inside the migration class > to keep them from clashing. This temp model gives me a nicer way to > manage the data, and frees me from worrying about filters, > validations, changing method names, etc.
Rick -- That's a really slick way to handle this problem! I'm going to have to give that a try. That makes my day. So -- any similarly slick ideas on how to handle the "I want to add a local migration without getting stomped by the upstream" issue I was jabbering about at the beginning? Thanks, Rick -- http://www.rickbradley.com MUPRN: 497 | all those negative random email haiku | vibes get you? <fade out> Seen | both movies. They rock. _______________________________________________ Rails-core mailing list Rails-core@lists.rubyonrails.org http://lists.rubyonrails.org/mailman/listinfo/rails-core
