On Thu, Mar 12, 2009 at 9:10 AM, Tekin Suleyman <te...@tekin.co.uk> wrote: > 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.
Unnecessarily copying a file from a plugin seems wrong. Referencing plugin migrations from your app (as Desert does) seems right. -- Chad --~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-core@googlegroups.com To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
