On 06/08/2010 08:39 PM, Richard Conroy wrote:
> On Mon, Jun 7, 2010 at 11:05 PM, Dave Howell
>> I still haven't figured out what, exactly, a Domain Model will do for me,
>> or even exactly what it is, but I'm not (deliberately? consciously?) trying
>> to throw those advantages away. Thanks for the links.
> 
> Having  model objects saves a LOT of coding. It gives you intuitive places
> to put validation. It integrates well into testing apis and makes the client
> side coding very tidy and natural. In addition you can get a lot of free
> features if you use an API like DM or AR (like SQL injection protection, or
> form helpers). Do not underestimate the saving in lines of code.

The problems occur when you go from a database schema to a domain model.
 All the major ORM frameworks are built on the assumption you will
confirm the database to the domain model, not the other way round. i.e.
Object Relational Mapping not Relational Object Mapping ;)

Legacy database mapping is hard and not something you should do unless
really necessary. i.e. you don't control the database and so can't chose
a reasonable schema.

Edward