I like to create my tables in MySQL, and not through Rails. I am hoping that I will still be able to get everything to work with this approach in Rails 2.0.
On Mar 6, 10:47 am, Cliff Rhyne <[EMAIL PROTECTED]> wrote: > I will admit that I didn't like the changes in the scaffold > initially. However, now that I've gotten my feet wet I think that it > was a good move. It moved everything in migration scripts and out of > a create.sql file. You can create scaffolds entirely via one command > (although it can be on the long side). > > I have mixed feelings about some of the changes to the views, but > overall I think they are better. It's not so much that they are bad, > but I need to learn more about them. > > On Mar 6, 10:27 am, tommy <[EMAIL PROTECTED]> wrote: > > > > > Yeah, do it! > > > There are some big improvements and it does not take long to convert > > it over. > > > scaffolding works a lot better now, it generates REST style MVCs now. > > > There is a performance upgrade too with mysql query caching support. > > > Google for the rake deprecated task. it will help. > > > tommy > > > On Mar 6, 10:18 am, liquid_rails <[EMAIL PROTECTED]> wrote: > > > > Has anyone made the switch over to Rails 2.0 yet? If so, I'd be > > > interested in hearing your thoughts about it. One difference that I > > > know of is that scaffolding a la Rails 1.* no longer works...- Hide > > > quoted text - > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ SD Ruby mailing list [email protected] http://groups.google.com/group/sdruby -~----------~----~----~----~------~----~------~--~---
