On Fri, 26 Jun 2015, Marcos Douglas wrote:
Things start to get messy when you start thinking about functionality.
So that comes next, and the business classes reflect functionality, and
consequently more susceptible to change.
Luckily the persistence layers I use are flexible enough to allow any
mapping between data and business objects,
so the above approach has always worked for me.
I'm tempted to say that working the other way round is bound to lead to
confusion.
Confusion... That depends if you work using a data-driven design or
behavior-driven design.
Always data.
Data exists on itself. Behaviour never exists on itself.
The moon is there, whether you look at it or not.
Michael.
--
_______________________________________________
Lazarus mailing list
[email protected]
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
