• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
merging changes upon a save: what are “locally uncommitted changes”, too many snapshots?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

merging changes upon a save: what are “locally uncommitted changes”, too many snapshots?


  • Subject: merging changes upon a save: what are “locally uncommitted changes”, too many snapshots?
  • From: OCsite via Webobjects-dev <email@hidden>
  • Date: Wed, 16 Jun 2021 21:23:48 +0200

Hi there,

is the process of merging changes upon a save into other ECs, and all the kinds
of snapshots available, documented somewhere in detail?

My old EOEditingContextConcepts says just this:

... However, locally uncommitted changes to objects in the EOEditingContext are
by default reapplied to the objects, in effect preserving the uncommitted
changes in the object graph. After the update, the uncommitted changes remain
uncommitted, but the committed snapshots have been updated to reflect the
values in the EOObjectStore.

and I can't see what does it actually mean “locally uncommitted changes” here.
Most probably a difference from some snapshot, but I admit I am sort of lost in
the things.

So far I lived in impression that (if we ignore undo) there's only one kind of
snapshots: OSC-level shared snapshots of what-was-just-saved-into-DB.

I've tried to research the thing a bit and there seem to be at the very least
the following snapshots:

(i) EC.committedSnapshotForObject
(ii) EC.currentEventSnapshotForObject
(iii) EODatabaseContext.snapshotForGlobalID
(iv) EODatabaseContext.localSnapshotForGlobalID

I regret to say the standard documentation does not help much. I did some
testing and it looks like

- (iii) is the one snapshot I knew: whenever save finishes, it always contains
the newly saved values
- (i) and (ii) — which for me always contain same data, that's weird! — seem to
contain an EC-level snapshot stored at its (first) willChange. Also it looks
like those “locally uncommitted changes” are based on (one of) these. So far
though I haven't found a case when (i) would differ from (ii)... although,
based on the name, I would actually presume (i) should be the same as (iii). It
very definitely is not.
- (iv) I don't understand at all :(

Are those things somewhere documented in detail?

Thanks and all the best,
OC

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Prev by Date: Re: [WO-DEV] old/invalid :1 relationship value, how the H. possible?!?
  • Next by Date: Re: WOLips bugfixes and new features planning
  • Previous by thread: Re: [WO-DEV] old/invalid :1 relationship value, how the H. possible?!?
  • Next by thread: Re: WOLips bugfixes and new features planning
  • Index(es):
    • Date
    • Thread