I thought that @count operates directly on the db, if the to-many is
still faulted... Am I mistaken about that? I am pretty sure I've read
it is optimized somehow, if not to do a count query on the db, then
how? And, if @count does it, why not @sum too?
On Apr 28, 2008, at 11:37, Pierre Bernard wrote:
Once you are in the OO world, you stay there: an optimization would
break if you were to have uncommited additions to "books"
How is this any different then doing a manual sum? Assuming that the
relationship is a fault, and optimized, EOF performs this operation
on the DB, you get the latest state saved to the DB. If it is not a
fault, you do it in memory, and get the latest state of the context
of the relationship's source. Either way, you get the latest of what
the context can be aware of. If there are uncommitted additions to
"books" in other contexts, you don't get those anyway, before they
are committed, right? So, what is the difference? Except for firing a
potentially large to-many fault unnecessarily...
Am I missing something?
F
_______________________________________________
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]
