On 11 Mar 2009, at 23:04, James Adam wrote: > > I've attached what I believe to be the simplest, least-intrusive > implementation I can think of to the ticket - > http://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/2058-rake-tasks-for-run-engine-migrations#ticket-2058-22 > > Please take a look, and let me know what you think.
This looks good to me, much neater than having separate tables or extra columns to maintain migrations from plugins.I think it's perfectly reasonable to expect a user of a plugin to copy the migrations that creates the models to their db/migrations directory. The only thing I can think of is potentially hooking this into the install script so that they automatically get copied across during installation of the plugin. Or is that too much magic? Cheers, Tekin Suleyman "See you at Scotland on Rails!" Ruby on Rails Developer +44 (0) 161 408 8868 +44 (0) 7968 355 460 http://tekin.co.uk --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
