Jerry W. Walker wrote:
Hi, Scott,
On Mar 7, 2006, at 8:16 PM, Scott Winn wrote:
In my experience, however, I've seen two approaches to all but the
primary rule of thumb above.
One says put all the relationships in your model as bi-directional and
prune them only if (and when) they cause problems. This approach tends
to make your initial coding easier because you can simply assume, for
any but a relationship to reference data, that the relationship is
bi-directional and use it as such (in the WO way :-) ) without
thinking about it a lot. When you find a problem, as you have,
determine the offending relationship and prune it. This approach tends
to be followed by the "Make it work, make it right, make it fast"
school of developers.
The other (followed by strong XP advocates) says to only add
relationships, and only in the direction required, that are needed to
complete the immediate requirement. Never add anything (relationship,
attribute, method, class and so forth) for some ill defined future
need. In XP terms, only add what's needed to implement the current
story and nothing more.
Hi Jerry,
Nice precis and helpful information. I'm not an advocate of XP and your
example above shows one of the reasons why. For me, the primary
objective is to model the data so that I understand what the customer is
saying, what I need to provide, and the best way to implement it.
Following the XP approach would lead to a rather ad hoc data model, IMHO.
Note that I am not saying put in all Entities you can imagine with every
conceivable relationship. My position is that you put in all the
Entities you know you need and all the relationships you think you need
as well. But I probably am of the MIW-MIR-MIF school of thought. Any
suggestions on how to pronounce that :-) ? mew-mer-mif...
-arturo
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
