You can put this in an initializer HoboFields::MigrationGenerator.ignore_tables = ['my_table', ... ]
Then the migration generator wont want to drop them. Tom On 8 Jun 2009, at 20:47, Steve VanB wrote: > > I have a live legacy system in place. > > I'd like to access, and modify some of the data with hobo. However > there are so many tables and fields, that to completely recreate all > the models in hobo would take weeks. I'd prefer to just create models > for tables as I need them. (or better yet, run a script that creates > all the models based on the tables currently in the database.) > > The hobo_migration script wants to drop all tables in the schema that > it doesn't know about. Something I don't want. > > How can I use hobo in such a legacy environment? > > Thanks! > > Steve. > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Hobo Users" 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/hobousers?hl=en -~----------~----~----~----~------~----~------~--~---
