|
in reply to Maybe database tables aren't such great "objects," after all ...
I forgot to mention that with most modern ORMs you don't have to be stuck having to think of one class = one table, they give you a lot of flexibility in how you want to map your entity class diagram. For example, do you want abstract classes to have their own table? You can if you want or you can tell the ORM to make each class hierarchy a single table. Do you want multiple classes to map to one table, you can. You can even have your entire entity class diagram be a single database table.
|
