Hi
>
> You are doing a fetch from the database -- I can't imagine a better time
> to update changed objects. Why not set the default behavior to check
What if the fetch would overwrite changes you are someone else was in
the midst of making? If you don't mind this then you can use the
refreshes refetched objects option on your fetch specs.
> for changed snapshots and update EOFs accordingly? The
> setRefreshesRefetchedObjects option is terribly inefficient as it causes
> all snapshots (changed or not) to be updated.
Actually All ECs share the same snapshots so 'all' snapshots for a given
row means exactly one object. if no EiditingContexts reference the
object then nothing else happens.
Note that since 'values' in a given EO (like decimal numbers, strings,
datas, dates, etc) are in fact also objects in most cases, your 'copies'
of EOs in different user ECs are actually mostly just filled with
references to the raw data in the shared snapshots.
d
