Personally I could see this staying pretty low priority. When it comes to converting legacy apps, the time is usually not in defining the database structure but in getting the rest of the app logic/views right. Would think non rails apps the db structure would be less than 1% of the total conversion time, for a rails app maybe 5%.
On Jul 16, 9:09 am, Owen <[email protected]> wrote: > We looked at adding this way back. In fact, I even talked to Dr Nic > about how much work it would be to customize his magic_model_generator > for Hobo over a year ago: > > http://github.com/drnic/magic_model_generator > > Other priorities and the fact that Rails 3 was on the horizon put this > on the back burner. I still think this would be very useful for > "Enterprise" developers and and plan to push for this in upcoming > releases. > > Of course, that doesn't help you right now. : -) > > On Jul 15, 2:41 pm, NewHoboUser <[email protected]> wrote: > > > Hi, all. Loving Hobo so far, but one thing I can't figure out. I > > have an existing database schema that conforms to Rails preferences > > quite well, and I want to generate hobo_model_resource's for it. Is > > there a trivial way to generate a model for an existing table so that > > the fields statement already incorporates the existing structure of > > the table? That is, without respecifying every single field in the > > initial generate hobo_model_resource statement. > > > I think I'm looking for a model equivalent of rake db:schema:dump. > > > Thank you! > > -- 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.
