It's VERY rare that I have the relationship modeled but don't want
the graph in sync.
We actually do it a lot. If you think about our system there are
some apps that spend 99% of their time
inserting data (think of when something is sold) and there are
others that spend 99% of their time reading
that same data (think of when something is invoiced). Those first
class of apps are not going to traverse
the object graph after the insert and need to be very fast. The
other class of apps will fetch and then
traverse the object graph and are not anywhere near as performance
sensitive.
Now I'm just going to have to go look into fixing this in Wonder. How
much effort is expended being scared of inverse faulting (which is a
problem that seems like it really shouldn't be all THAT hard to fix
with a little elbow grease)?
ms
_______________________________________________
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]
