On Thu, Aug 12, 2010 at 10:15:24PM +0200, Robert Walker wrote: > Ludek Vodicka wrote: > > ORM Designer serves to design ORM model definitions. Instead of writing > > definitions to several text files, you will be able to design your model > > in one place and then export it. > > I think you'll find that your tool is designed to solve a problem that > doesn't exist in Ruby on Rails. One of the primary advantages of > ActiveRecord is convention over configuration. There is not a bunch of > text files storing model configurations. [...] > And that is all there is to it. ActiveRecord will get everything it > needs to know from the database. There is no configuration file.
That's true for ActiveRecord, but Rails3 supports much more than AR. DataMapper, for example, could benefit from such a tool. --Greg -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" 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/rubyonrails-talk?hl=en.
