> > Thank you Frans! Even as a noob in the ORM sphere, I have always felt
this
> > way, and in fact wanted interject into this discussion before you said
this.
> > In my years as a designer/developer, I have very, very seldom ever seen
> > changes to the DB entity that do not require changes to the class. The
> > changes are business driven, and when the client wants a change to their
> > Person, it always requires a change to the class and the entity, because
the
> > Person they both represent changes.
>
> Could this be because you are/were working in a data centric world?
What's 'data centric' ?
> I regularly see changes in database structure that do not represent
> changes in my domain. An example of this might be selective
> denormalization for optimization on a small system or the pulling out
> of something that was columns into a new joined table.
Ah, and denormalization side effects like multiple rows with the same
data of the same entity aren't a problem in your code, because that's
transparently solved? I don't think so.
FB
===================================
This list is hosted by DevelopMentor® http://www.develop.com
View archives and manage your subscription(s) at http://discuss.develop.com
