The purpose of my investigation was to incorporate an ORM into an MVC. I like what rails did mutating the both of them into one. But, I think they choose the worst ORM to do so. I don't like the fact that I'm supposed to design in an app, and roll changes to a db.
First off, Rails doesn't mutate the ORM into an MVC - rails just makes it easy to generate a Model View and Controller classes based on a database table. You don't have to generate each, and in my view the Model classgeneration is probably the most useful.
Secondly, If you don't change the DB, you're free to change the (possibly generated) classes as you see fit, but if you do change a DB table's fields, the model changes automatically with it (via ActiveRecord).
Maybe I'm misinterpreting that part of your post, but I don't really see what you mean there.
In reply to Re: Non-retarded ORMs, and a general ORM discussions.
by Joost
in thread Non-retarded ORMs, and a general ORM discussions.
by EvanCarroll
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |