There's no reason why you can't drop or add columns to the tables which are created by the engine migrations - you just need to be careful about the order in which you migrate your systems (i.e. probably engines first, and then your specific application migrations second).
- james On 3/10/06, Keith Lancaster <[EMAIL PROTECTED]> wrote: > Before I strike out and try to invent something, I wanted to know if > anybody had addressed this issue. > > We are using the login/user engines to manage security, etc. We have a > need to add columns to the user and permissions tables. Is there any > standard way to override / augment the engine migrations *without* > hacking those in the vendor directory? IOW, I'd like to add/override > some migration functions in some way similar to the way we override > views/controllers. > > Any thoughts? > > Keith > > -- > Posted via http://www.ruby-forum.com/. > _______________________________________________ > engine-users mailing list > [email protected] > http://lists.rails-engines.org/listinfo.cgi/engine-users-rails-engines.org > -- * J * ~ _______________________________________________ engine-users mailing list [email protected] http://lists.rails-engines.org/listinfo.cgi/engine-users-rails-engines.org
