assuming you're talking specifically about hobo fields. if your fields match your schema, there should be no changes (though maybe some index additions if you don't already have foreign keys indexed).
since hobo is a rails extension and leaves all normal rails functionality, you should be able to install it and leave all your existing code in place. then you can replace pieces with dryml, lifecycles, etc. as you see fit. On Jul 19, 12:20 pm, develgenius <[email protected]> wrote: > Hi, > > We have an old Rails application (developed in 2005) and we would like > to revamp it using Hobo. We are starting to read Hobo's manual and > learn more about it but one concern that we have is that because this > application is live, we don't want to make any intrusive changes to > the database. We would like to develop the new application while the > old one is running. Do the Hobo generators support that? When we > generate our resources and we specify all the fields in our current > tables, will Hobo learn from them so that it doesn't "destroy" any > data? > > Thanks, > JD -- 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.
