DataContext.currentSnapshot() fails to set created snapshot entity name. This causes confusion downstream. One obscure case that I was finally able to trace to this issue was related to inheritance:
- "currentSnapshot" was called for concrete subclass during new object commit.
- returned snapshot ended up in the shared cache
- later a RelationshipQuery for another object pointing to this one received the snapshot from cache.
- The result was the attempt to instantiate an abstract superclass instead of subclass
So we need to fix 'currentSnapshot' and maybe also add sanity checks to "objectsFromDataRows" to throw on invalid snapshots.