Yowser. Thanks to both of you - that's exactly what I mean. Any
pointers on where I can find an example of a class that is unaware
if it is in the db? Or is there a good example of the second
solution, of a single class that does the what and why, and an
interchangeable layer/context
On Monday 10 December 2007 12:12:19 Paul-Michael Agapow wrote:
Yowser. Thanks to both of you - that's exactly what I mean. Any
pointers on where I can find an example of a class that is
unaware if it is in the db? Or is there a good example of the
second solution, of a single class that does
Hi,
A Sample may be created by the web application or fetched from the
database. Later on, it may be disposed of, edited or checked back into
the db.
On the other hand, the requirements and coding of both classes are
kinda different, and I find myself changing the properties of the
Paul Johnston wrote:
Hi,
A Sample may be created by the web application or fetched from the
database. Later on, it may be disposed of, edited or checked back into
the db.
On the other hand, the requirements and coding of both classes are
kinda different, and I find myself changing
