-
Notifications
You must be signed in to change notification settings - Fork 308
/
ODOEditingContext.m
2200 lines (1752 loc) · 99.7 KB
/
ODOEditingContext.m
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
// Copyright 2008-2021 Omni Development, Inc. All rights reserved.
//
// This software may only be used and reproduced according to the
// terms in the file OmniSourceLicense.html, which should be
// distributed with this project and can also be found at
// <http://www.omnigroup.com/developer/sourcecode/sourcelicense/>.
#import <OmniDataObjects/ODOEditingContext.h>
#import <OmniDataObjects/ODOEditingContext-Subclass.h>
#import <OmniDataObjects/ODOFetchRequest.h>
#import <OmniDataObjects/ODOObject.h>
#import <OmniDataObjects/ODOObjectID.h>
#import <OmniDataObjects/ODORelationship.h>
#import <OmniDataObjects/NSPredicate-ODOExtensions.h>
#import <OmniDataObjects/ODOModel.h>
#import <OmniDataObjects/Errors.h>
@import OmniBase;
@import OmniFoundation;
@import Foundation;
#import "ODOProperty-Internal.h"
#import "ODOEditingContext-Internal.h"
#import "ODOObject-Accessors.h"
#import "ODOObject-Internal.h"
#import "ODODatabase-Internal.h"
#import "ODOEntity-SQL.h"
#import "ODOSQLStatement.h"
#import "ODOInternal.h"
#if TARGET_OS_IPHONE
#import <objc/message.h>
#endif
#if 0 && defined(DEBUG)
#define DEBUG_DELETE(format, ...) NSLog((format), ## __VA_ARGS__)
#else
#define DEBUG_DELETE(format, ...) do {} while (0)
#endif
#import <sqlite3.h>
RCS_ID("$Id$")
OFDeclareDebugLogLevel(ODOEditingContextOwnershipCheckingDisabled);
NS_ASSUME_NONNULL_BEGIN
@implementation ODOEditingContext
{
// Remember the runloop we added an observer on for assertions.
CFRunLoopRef _runLoopForObserver;
CFRunLoopObserverRef _runLoopObserver;
}
- (instancetype)initWithDatabase:(ODODatabase *)database;
{
OBPRECONDITION(database);
if (!(self = [super init]))
return nil;
// TODO: Register with the database so we can ensure there is only one editing context at a time (not supporting edit merging).
_database = [database retain];
// If the database is disconnected from its file, we need to forget our contents.
[[NSNotificationCenter defaultCenter] addObserver:self selector:@selector(_databaseConnectionDidChange:) name:ODODatabaseConnectedURLChangedNotification object:_database];
_registeredObjectByID = [[NSMutableDictionary alloc] init];
OBINVARIANT([self _checkInvariants]);
return self;
}
- (void)dealloc;
{
OBPRECONDITION(_owningQueue == NULL);
OBPRECONDITION(_saveDate == nil);
OBINVARIANT([self _checkInvariants]);
// TODO: Deregister with the database so we can ensure there is only one editing context at a time (not supporting edit merging).
[[NSNotificationCenter defaultCenter] removeObserver:self name:ODODatabaseConnectedURLChangedNotification object:_database];
[_database release];
[_undoManager removeAllActionsWithTarget:self];
[_undoManager release];
if (_runLoopObserver) {
[self _removeRunLoopObserver];
}
[_registeredObjectByID release];
OBASSERT([_processedInsertedObjects count] == 0);
OBASSERT([_processedUpdatedObjects count] == 0);
OBASSERT([_processedDeletedObjects count] == 0);
[_processedInsertedObjects release];
[_processedUpdatedObjects release];
[_processedDeletedObjects release];
OBASSERT([_recentlyInsertedObjects count] == 0);
OBASSERT([_recentlyUpdatedObjects count] == 0);
OBASSERT([_recentlyDeletedObjects count] == 0);
[_recentlyInsertedObjects release];
[_recentlyUpdatedObjects release];
[_recentlyDeletedObjects release];
[_label release];
[super dealloc];
}
- (void)assumeOwnershipWithQueue:(dispatch_queue_t)queue;
{
if (ODOEditingContextOwnershipCheckingDisabled > 0) {
return;
}
OBRecordBacktraceWithContext("Assume ownership", OBBacktraceBuffer_Generic, self);
assert(_owningQueue == NULL);
assert(queue != NULL);
dispatch_assert_queue(queue);
dispatch_retain(queue);
_owningQueue = queue;
}
- (void)relinquishOwnerhip;
{
if (ODOEditingContextOwnershipCheckingDisabled > 0) {
return;
}
OBRecordBacktraceWithContext("Relinquish ownership", OBBacktraceBuffer_Generic, self);
assert(_owningQueue != NULL);
dispatch_assert_queue(_owningQueue);
dispatch_release(_owningQueue);
_owningQueue = NULL;
}
void ODOEditingContextAssertOwnership(ODOEditingContext *context)
{
if (ODOEditingContextOwnershipCheckingDisabled > 0) {
return;
}
dispatch_assert_queue(context->_owningQueue);
}
BOOL ODOEditingContextExecuteWithOwnership(ODOEditingContext *self, dispatch_queue_t temporaryOwner, BOOL (^ NS_NOESCAPE action)(void))
{
if (ODOEditingContextOwnershipCheckingDisabled > 0) {
return action();
}
// This could be done with methods above, but this will log fewer backtrace buffers and will be slightly more efficient, if it matters.
// OBRecordBacktraceWithContext("Yield ownership", OBBacktraceBuffer_Generic, self);
// Make sure we start out on the current owning queue and then swap in the new owner.
// We *probably* don't need to retain the temporary owner, but will for now.
dispatch_queue_t originalQueue = self->_owningQueue; // still retained
dispatch_assert_queue(originalQueue);
self->_owningQueue = temporaryOwner;
dispatch_retain(temporaryOwner);
// This is assumed to dispatch to the temporary owner queue to do some work and synchronously wait for the result.
BOOL result = action();
dispatch_release(temporaryOwner);
self->_owningQueue = originalQueue; // still retained from above
return result;
}
- (BOOL)executeWithTemporaryOwnership:(dispatch_queue_t)temporaryOwner operation:(BOOL (^)(void))operation;
{
return ODOEditingContextExecuteWithOwnership(self, temporaryOwner, operation);
}
- (ODODatabase *)database;
{
ODOEditingContextAssertOwnership(self);
OBPRECONDITION(_database);
return _database;
}
- (nullable NSUndoManager *)undoManager;
{
ODOEditingContextAssertOwnership(self);
return _undoManager;
}
- (void)setUndoManager:(nullable NSUndoManager *)undoManager;
{
OBRecordBacktraceWithContext("Editing context", OBBacktraceBuffer_Generic, (const void *)self);
OBRecordBacktraceWithContext("Set undo manager", OBBacktraceBuffer_Generic, (const void *)undoManager);
ODOEditingContextAssertOwnership(self);
if (_undoManager != nil) {
[_undoManager removeAllActionsWithTarget:self];
[_undoManager release];
_undoManager = nil;
}
_undoManager = [undoManager retain];
}
- (BOOL)automaticallyProcessPendingChanges;
{
ODOEditingContextAssertOwnership(self);
return _runLoopObserver != NULL;
}
- (void)setAutomaticallyProcessPendingChanges:(BOOL)automaticallyProcessPendingChanges;
{
ODOEditingContextAssertOwnership(self);
if (automaticallyProcessPendingChanges && _runLoopObserver == NULL) {
[self _addRunLoopObserver];
} else if (!automaticallyProcessPendingChanges && _runLoopObserver != NULL) {
[self _removeRunLoopObserver];
}
}
// Empties the reciever of all objects.
- (void)reset;
{
ODOEditingContextAssertOwnership(self);
OBINVARIANT([self _checkInvariants]);
// This cleanup can cause us to be deallocated if there are no other strong references
OBRetainAutorelease(self);
// Give observers a chance to clear caches of objects we are about to obliterate. During this time, if any fetching is attempted on us, we'll return nil. It's important to do the reset in two phases like this for the case of cascading caches; clearing cache A may invoke KVO that would cause messages to objects in cache B. If the objects in B are already invalidated, then bad things happen. This lets everyone shut down and then start up again.
_isResetting = YES;
@try {
[[NSNotificationCenter defaultCenter] postNotificationName:ODOEditingContextWillResetNotification object:self];
// Let objects know that the entire context is going away
for (ODOObject *object in [_registeredObjectByID objectEnumerator]) {
[object prepareForReset];
}
// Clear any undos we have logged
[_undoManager removeAllActionsWithTarget:self];
// get rid of pending, processed changes and snapshots
[_objectIDToCommittedPropertySnapshot release];
_objectIDToCommittedPropertySnapshot = nil;
[_objectIDToLastProcessedSnapshot release];
_objectIDToLastProcessedSnapshot = nil;
[_processedInsertedObjects release];
_processedInsertedObjects = nil;
[_processedUpdatedObjects release];
_processedUpdatedObjects = nil;
[_processedDeletedObjects release];
_processedDeletedObjects = nil;
[_recentlyInsertedObjects release];
_recentlyInsertedObjects = nil;
[_recentlyUpdatedObjects release];
_recentlyUpdatedObjects = nil;
[_recentlyDeletedObjects release];
_recentlyDeletedObjects = nil;
[_reinsertedObjects release];
_reinsertedObjects = nil;
_nonretainedLastRecentlyInsertedObject = nil;
// get rid of database metadata changes
[_database _discardPendingMetadataChanges];
// invalidate all registered objects
for (ODOObject *object in [_registeredObjectByID objectEnumerator])
[object _invalidate];
[_registeredObjectByID removeAllObjects];
if (_runLoopObserver) {
[self _removeRunLoopObserver];
}
} @finally {
_isResetting = NO;
}
// Give observers a chance to refill caches now that all listeners have had a chance to clear their caches.
[[NSNotificationCenter defaultCenter] postNotificationName:ODOEditingContextDidResetNotification object:self];
}
static void ODOEditingContextInternalInsertObject(ODOEditingContext *self, ODOObject *object, ODOObjectSnapshot **outMostRecentSnapshot)
{
OBPRECONDITION([self isKindOfClass:[ODOEditingContext class]]);
OBPRECONDITION([object isKindOfClass:[ODOObject class]]);
OBPRECONDITION([object editingContext] == self);
OBPRECONDITION(!self->_isValidatingAndWritingChanges); // Can't make edits in the validation methods
OBPRECONDITION(![self->_processedInsertedObjects member:object]);
OBPRECONDITION(![self->_recentlyInsertedObjects member:object]);
OBPRECONDITION(![self->_processedUpdatedObjects member:object]);
OBPRECONDITION(![self->_recentlyUpdatedObjects member:object]);
OBPRECONDITION(![self->_processedDeletedObjects member:object]);
OBPRECONDITION(![self->_recentlyDeletedObjects member:object]);
// TODO: Verify that the object being inserted isn't some old dead invalidated object (previously deleted and a save happened since then).
// Check to see if we are re-inserting something which was previously marked for deletion
ODOObject *previouslyRegisteredObject = [self->_registeredObjectByID objectForKey:[object objectID]];
if (previouslyRegisteredObject != nil) {
// Assert that the object we are trying to "replace" has been deleted. If this is not the case, we'll be severely messing up the lifecycle messages, so this is a hard assert.
assert([self->_recentlyDeletedObjects containsObject:previouslyRegisteredObject] || [self->_processedDeletedObjects containsObject:previouslyRegisteredObject]);
// This can't be a cancelled insert since those never make it into the deleted objects sets.
// Do this before altering the sets so that -willSave will set _flags.hasStartedDeletion.
[previouslyRegisteredObject willDelete:ODOWillDeleteEventMaterial];
[self->_recentlyDeletedObjects removeObject:previouslyRegisteredObject];
[self->_processedDeletedObjects removeObject:previouslyRegisteredObject];
ODOEditingContextDidDeleteObjects(self, [NSSet setWithObject:previouslyRegisteredObject]);
if (outMostRecentSnapshot != NULL) {
// Try last-processed first, falling back to committed, since that's effectively "reverse chronological"
ODOObjectSnapshot *mostRecentSnapshot = self->_objectIDToLastProcessedSnapshot[previouslyRegisteredObject.objectID];
if (mostRecentSnapshot == nil) {
mostRecentSnapshot = self->_objectIDToCommittedPropertySnapshot[previouslyRegisteredObject.objectID];
}
*outMostRecentSnapshot = [[mostRecentSnapshot retain] autorelease];
}
self->_objectIDToLastProcessedSnapshot[previouslyRegisteredObject.objectID] = nil;
self->_objectIDToCommittedPropertySnapshot[previouslyRegisteredObject.objectID] = nil;
// Record this object as a re-insert so we can do the right thing at save time
if (self->_reinsertedObjects == nil) {
self->_reinsertedObjects = [[NSMutableSet alloc] init];
}
[self->_reinsertedObjects addObject:object];
}
// Register and add it to the recent set
if (self->_recentlyInsertedObjects == nil) {
self->_recentlyInsertedObjects = ODOEditingContextCreateRecentSet(self);
}
[self->_recentlyInsertedObjects addObject:object];
self->_nonretainedLastRecentlyInsertedObject = object;
[self _registerObject:object];
}
// This is the global first-time insertion hook. This should only be called with *new* objects. That is, the undo of a delete should *not* go through here since that would re-call the -awakeFromInsert method.
- (void)_insertObject:(ODOObject *)object;
{
ODOEditingContextAssertOwnership(self);
OBINVARIANT([self _checkInvariants]);
// We don't allow re-inserted previously deleted objects. Even on undo of a delete, we make a new object and apply a snapshot to it.
OBASSERT(object->_flags.isFault == NO);
OBASSERT(object->_flags.hasStartedDeletion == NO);
OBASSERT(object->_flags.hasFinishedDeletion == NO);
OBASSERT(object.isDeleted == NO);
// Record the pointers of objects being inserted in case save validation fails and we need to know where it came from.
OBRecordBacktraceWithContext(class_getName(object_getClass(object)), OBBacktraceBuffer_Generic, (const void *)object);
// If we want an undeletable object, we need to make sure it can't be deleted via undo of this insert
BOOL undeletable = _ODOObjectIsUndeletable(object);
if (undeletable) {
// Close out this undo group
while ([self hasUnprocessedChanges])
[self processPendingChanges];
// Disable undo
[_undoManager disableUndoRegistration];
}
@try {
ODOObjectSnapshot *priorSnapshot = nil;
ODOEditingContextInternalInsertObject(self, object, &priorSnapshot);
OBASSERT(![object _isAwakingFromInsert]);
[object _setIsAwakingFromInsert:YES];
@try {
[object awakeFromInsert];
if ([_reinsertedObjects containsObject:object]) {
[object awakeFromEvent:ODOAwakeEventReinsertion snapshot:priorSnapshot];
}
} @finally {
[object _setIsAwakingFromInsert:NO];
}
// If this was to be undeletable, make sure it gets processed while undo is off
if (undeletable) {
while (_recentlyInsertedObjects || _recentlyUpdatedObjects || _recentlyDeletedObjects) {
[self processPendingChanges];
}
}
} @finally {
if (undeletable)
[_undoManager enableUndoRegistration];
}
OBINVARIANT([self _checkInvariants]);
}
static void _addNullify(ODOObject *owner, NSString *toOneKey, NSMutableDictionary *relationshipsToNullifyByObjectID)
{
OBPRECONDITION(owner);
OBPRECONDITION(toOneKey);
OBPRECONDITION([[[owner entity] relationshipsByName] objectForKey:toOneKey]);
OBPRECONDITION([[[[owner entity] relationshipsByName] objectForKey:toOneKey] isToMany] == NO);
OBPRECONDITION(relationshipsToNullifyByObjectID);
ODOObjectID *ownerID = [owner objectID];
NSMutableArray *keys = [relationshipsToNullifyByObjectID objectForKey:ownerID];
if (!keys) {
keys = [[NSMutableArray alloc] initWithObjects:&toOneKey count:1];
[relationshipsToNullifyByObjectID setObject:keys forKey:ownerID];
[keys release];
} else
[keys addObject:toOneKey];
}
// Adds a note that object.rel->dest would deny.
static void _addDenyNote(ODOObject *object, ODORelationship *rel, ODOObject *dest, NSMutableDictionary *denyObjectIDToReferer)
{
OBPRECONDITION(object);
OBPRECONDITION(rel);
OBPRECONDITION(dest);
OBPRECONDITION(denyObjectIDToReferer);
OBPRECONDITION([object editingContext] == [dest editingContext]);
OBPRECONDITION([object entity] == [rel entity]);
OBPRECONDITION([rel destinationEntity] == [dest entity]);
OBPRECONDITION([rel deleteRule] == ODORelationshipDeleteRuleDeny);
// We are unable to delete object due to the presence of 'dest' across the relationship 'rel'. Make a note of this for later.
// If there are multiple reasons to deny the deletion of 'object', only the last one will be noted for now.
// Note that the object that is the cause of the deny is the one used for the key; the one being denied is in the value. This makes it easy to clean up the case where the cause-of-deny object was deleted already.
NSArray *info = [[NSArray alloc] initWithObjects:[rel name], [object objectID], nil];
[denyObjectIDToReferer setObject:info forKey:[dest objectID]];
[info release];
}
typedef struct {
ODOEditingContext *self;
BOOL fail;
NSError * _Nullable error;
NSMutableSet *toDelete;
NSMutableDictionary *relationshipsToNullifyByObjectID;
NSMutableDictionary *denyObjectIDToReferer;
} TraceForDeletionContext;
static void _traceForDeletion(ODOObject *object, TraceForDeletionContext *ctx);
static void _traceToManyRelationship(ODOObject *object, ODORelationship *rel, TraceForDeletionContext *ctx)
{
OBPRECONDITION([rel isToMany]);
// This is what to do to the *destination* of the relationship
ODORelationshipDeleteRule rule = [rel deleteRule];
ODORelationship *inverseRel = [rel inverseRelationship];
NSString *forwardKey = [rel name];
NSString *inverseKey = [inverseRel name];
if (rule == ODORelationshipDeleteRuleDeny) {
OBASSERT([inverseRel isToMany] == NO); // We don't allow many-to-many relationships in the model loading code
OBFinishPorting; // Handle once we have a test case
}
BOOL alsoCascade;
if (rule == ODORelationshipDeleteRuleNullify) {
alsoCascade = NO;
} else if (rule == ODORelationshipDeleteRuleCascade) {
alsoCascade = YES;
} else {
OBASSERT_NOT_REACHED("Expected to identify the delete rule in question"); // unknown delete rule
}
// Nullify all the inverse to-ones.
OBASSERT([inverseRel isToMany] == NO); // We don't allow many-to-many relationships in the model loading code
OBASSERT([inverseRel isCalculated] == NO); // since the to-many is effectively calculated from the to-one, this would be silly.
NSSet *targets = [object valueForKey:forwardKey];
OBASSERT([targets isKindOfClass:[NSSet class]]);
for (ODOObject *target in targets) {
if (![inverseRel isCalculated])
_addNullify(target, inverseKey, ctx->relationshipsToNullifyByObjectID);
if (alsoCascade && !_ODOObjectIsUndeletable(target))
_traceForDeletion(target, ctx);
}
}
static void _traceToOneRelationship(ODOObject *object, ODORelationship *rel, TraceForDeletionContext *ctx)
{
OBPRECONDITION(![rel isToMany]);
// This is what to do to the *destination* of the relationship
ODORelationshipDeleteRule rule = [rel deleteRule];
ODORelationship *inverseRel = [rel inverseRelationship];
NSString *forwardKey = [rel name];
NSString *inverseKey = [inverseRel name];
if (rule == ODORelationshipDeleteRuleNullify) {
if ([inverseRel isToMany]) {
// We have a to-one and we need to remove ourselves from the inverse to-many. In the past, we used to force clearing the inverse to-many fault, even if our to-one itself was a fault. But, if our to-one is still a fault, it can't hold a reference back to us (and any future fetches will get filtered vs. the deleted objects). Forcing the inverse to-many to be cleared may not be necessary here either.
ODOObject *dest = [object valueForKey:forwardKey];
if (dest) {
if (![dest isFault]) {
#ifdef OMNI_ASSERTIONS_ON
NSSet *inverseSet =
#endif
[dest valueForKey:inverseKey]; // clears the fault
OBASSERT([inverseSet member:object] == object);
}
_addNullify(object, forwardKey, ctx->relationshipsToNullifyByObjectID);
}
} else {
// one-to-one relationship. one side should be marked as calculated.
OBASSERT([rel isCalculated] || [inverseRel isCalculated]);
ODOObject *dest = [object valueForKey:forwardKey];
if (dest) {
// nullify the side that isn't calculated. we could maybe not do the nullify it is is the forward relationship (since the owner is getting entirely deleted).
if (![rel isCalculated])
_addNullify(object, forwardKey, ctx->relationshipsToNullifyByObjectID);
if (![inverseRel isCalculated])
_addNullify(dest, inverseKey, ctx->relationshipsToNullifyByObjectID);
}
}
return;
}
// We treat cascading a delete onto an undeletable object as a nullify instead.
// Also, when cascading will nullify to-one relationships too. This ensures that any KVO registrations can be cleaned up properly.
if (rule == ODORelationshipDeleteRuleCascade) {
ODOObject *dest = [object valueForKey:forwardKey];
if (dest) {
if (![rel isCalculated])
_addNullify(object, forwardKey, ctx->relationshipsToNullifyByObjectID);
if (!_ODOObjectIsUndeletable(dest))
_traceForDeletion(dest, ctx);
}
return;
}
if (rule == ODORelationshipDeleteRuleDeny) {
ODOObject *dest = [object valueForKey:forwardKey];
if (dest)
_addDenyNote(object, rel, dest, ctx->denyObjectIDToReferer);
return;
}
OBASSERT_NOT_REACHED("Expected to identify the delete rule in question"); // unknown delete rule
}
static void _traceForDeletion(ODOObject *object, TraceForDeletionContext *ctx)
{
OBPRECONDITION(!_ODOObjectIsUndeletable(object));
// Someone already failed?
if (ctx->fail)
return;
// Avoid problems with cycles
if ([ctx->toDelete member:object])
return;
[ctx->toDelete addObject:object];
ODOEntity *entity = [object entity];
NSArray *relationships = [entity relationships];
for (ODORelationship *rel in relationships) {
if ([rel isToMany])
_traceToManyRelationship(object, rel, ctx);
else
_traceToOneRelationship(object, rel, ctx);
if (ctx->fail)
return; // no point going on.
}
}
// Turns out none of our objects implement -validateForDelete: right now.
#if 0
typedef struct {
BOOL failed;
NSError *error;
} ValidateForDeleteApplierContext;
static void _validateForDeleteApplier(const void *value, void *context)
{
ODOObject *object = (ODOObject *)value;
ValidateForDeleteApplierContext *ctx = context;
if (ctx->failed)
return;
if (![object validateForDelete:&ctx->error])
ctx->failed = YES;
}
#endif
- (void)_snapshotObjectForDeletion:(ODOObject *)object;
{
// Reject if object is undeletable... should not have gotten this far. This means all undeletable objects must be inserted w/o undo enabled or having undo flushed afterwards.
if (_ODOObjectIsUndeletable(object))
OBRejectInvalidCall(self, _cmd, @"Undeletable objects should not be deleted!");
#ifdef OMNI_ASSERTIONS_ON
// All the to-one relationships must be nil at this point. Otherwise, observation across a keyPath won't trigger due to objects along that keyPath being deleted and we might leak observation info. Additionally, when a 'did delete' notification goes out and the observer removes its observed keyPath, the crossings of to-one relationships can return nil and be correct w/o asserting about asserting that we aren't doing KVC on deleted objects.
for (ODORelationship *rel in object.entity.toOneRelationships) {
ODOObject *destination = _ODOObjectGetObjectValueForProperty(object, rel);
OBASSERT(destination == nil);
}
#endif
// Might have been snapshotted if we had a recent or processed update. Since we are about to delete it, it is already in the _recentlyDeletedObjects set and has been remove from _recentlyUpdatedObjects.
// OBASSERT(([_objectIDToCommittedPropertySnapshot objectForKey:[object objectID]] == nil && [_objectIDToLastProcessedSnapshot objectForKey:[object objectID]] == nil) == ([_recentlyUpdatedObjects member:object] == nil && [_processedUpdatedObjects member:object] == nil));
[self _snapshotObjectPropertiesIfNeeded:object];
// We used to turn deleted objects into faults here and release all their properties. But SwiftUI Views that are given access to ODOObjects can end up being evaluated again unpredictably, causing crashes that are difficult to solve. Instead, deleted objects now are left with their properties intact and relationships cleared (firing KVO to clean up dependent key path observations, but *not* propagating those changes to the ObjectWillChangePublisher and possibly provoking more View evaluations).
}
static void _removeDenyApplier(const void *value, void *context)
{
ODOObject *deletedObject = (ODOObject *)value;
NSMutableDictionary *denyObjectIDToReferer = (NSMutableDictionary *)context;
[denyObjectIDToReferer removeObjectForKey:[deletedObject objectID]];
}
static void _nullifyRelationships(const void *dictKey, const void *dictValue, void *context)
{
ODOObjectID *objectID = (ODOObjectID *)dictKey;
NSArray *toOneKeys = (NSArray *)dictValue;
TraceForDeletionContext *ctx = context;
DEBUG_DELETE(@"DELETE: nullify %@ %@", [objectID shortDescription], toOneKeys);
ODOObject *object = [ctx->self->_registeredObjectByID objectForKey:objectID];
OBASSERT(object != nil);
if (object == nil) {
return;
}
// Any objects that were to get relationships nullified don't need to be nullified if they are also getting deleted.
// Actually, this is false. If we have an to-one, we need to nullify it so that the inverse to-many has a KVO cycle. Otherwise, the to-many holder won't get in the updated set, or advertise its change. Also, we need to publicize the to-one going to nil so that multi-stage KVO keyPath observations will stop their subpath observing.
//if ([ctx->toDelete member:object])
//return;
NSMutableSet<ODORelationship *> *toOneRelationships = [NSMutableSet set];
NSDictionary<NSString *, ODORelationship *> *relationshipsByName = object.entity.relationshipsByName;
for (NSString *key in toOneKeys) {
ODORelationship *relationship = relationshipsByName[key];
OBASSERT(relationship != nil);
OBASSERT([relationship isToMany] == NO);
if (relationship != nil && ![relationship isToMany]) {
[toOneRelationships addObject:relationship];
}
}
[object willNullifyRelationships:toOneRelationships];
for (ODORelationship *rel in toOneRelationships) {
NSString *key = rel.name;
// If we are getting deleted, then use the internal path for clearing the forward relationship instead of calling the setter. But, if we are going to stick around (we are on the fringe of the delete cloud), call the setter.
if ([ctx->toDelete member:object]) {
[object willChangeValueForKey:key];
ODOObjectSetPrimitiveValueForProperty(object, nil, rel);
[object didChangeValueForKey:key];
} else {
[object setValue:nil forKey:key];
}
}
[object didNullifyRelationships:toOneRelationships];
}
// This just registers the deletes and gathers snapshots for them. Used both in the public API and in the undo support
static void ODOEditingContextInternalDeleteObjects(ODOEditingContext *self, NSSet *toDelete)
{
DEBUG_DELETE(@"DELETE: internal delete %@", [toDelete setByPerformingSelector:@selector(shortDescription)]);
// Before calling out to our observer with the "will be deleted" notification, add the object we're deleting to our set of recently deleted objects--and remove it from our recently updated objects. This means that it's safe for the observer to call -processPendingChanges without getting a bogus "object changed" notification.
// (In <bug:///98546> (Crash updating forecast/inbox badge after sync? -[HomeController _forecastCount]), the observer was the OFMLiveFetch for overdue objects, and it removed the deleted object from its object set. Great, this is what we want. This fired off the OFMLiveFetchObjectsBinding, which was seen by HomeController and triggered a refresh of the badges for visible nodes. HomeController was asking AppController for the set of overdue tasks. Still, so far so good. But then -overdueTasks was calling back to our -processPendingChanges which was firing off a notification which included this deleted object in its update set (failing an assertion, since this method was supposed to guarantee that couldn't happen). So then the OFMLiveFetch for overdue tasks saw the update for our not-yet-deleted object, and added it back to its set. After -processPendingChanges returned, -overdueTasks tried to sort the returned task by due date and hit this deleted object and... kaboom!)
if (!self->_recentlyDeletedObjects)
self->_recentlyDeletedObjects = ODOEditingContextCreateRecentSet(self);
// Before this, the objects shouldn't claim to be deleted.
#ifdef OMNI_ASSERTIONS_ON
for (ODOObject *object in toDelete)
OBASSERT(![object isDeleted]);
#endif
// Still shouldn't have any insertions, but we might have some locally created updates. Some of these may now be overridden by our deletions (but the updates to their inverses won't be).
OBASSERT(!self->_recentlyInsertedObjects);
[self->_recentlyDeletedObjects unionSet:toDelete];
[self->_recentlyUpdatedObjects minusSet:toDelete];
// Now they should so that observers of the notification can't remove objects in response to the notification, then trigger a fetch that would find the objects and accidentally re-add them. A possibly better long-term fix for this would be to have a pending-deletes list that we'd use to filter fetches and such.
#ifdef OMNI_ASSERTIONS_ON
for (ODOObject *object in toDelete) {
OBASSERT([object isDeleted]);
OBASSERT([self _isBeingDeleted:object]);
}
#endif
// If someone calls back into -processPendingChanges, we're going to try to register undos for objects from our set of recently deleted objects. Those undos will need to reference snapshots, so we'd better add those snapshots now. Fixes <bug:///99138> (Regression: Exception when trying to syncing after deleting an inbox task (Assert failed: requires snapshot) [_registerUndoForRecentChanges]).
for (ODOObject *object in toDelete) {
// Record the pointers of objects being deleted in case someone accesses one soon and crashes
OBRecordBacktraceWithContext(class_getName(object_getClass(object)), OBBacktraceBuffer_Generic, (const void *)object);
[self _snapshotObjectPropertiesIfNeeded:object];
}
// Some objects (I'm looking at you NSArrayController) are dumb as posts and if you clear their content, they'll ask their old content questions like, "Hey; what's your value for this key?". That doesn't work well for deleted objects. CoreData has some hack into NSArrayController to avoid this, we need something of the like. For now we'll post a note before finalizing the deletion.
NSDictionary *userInfo = _createChangeSetNotificationUserInfo(nil, nil, toDelete, self->_objectIDToCommittedPropertySnapshot, self->_objectIDToLastProcessedSnapshot);
[[NSNotificationCenter defaultCenter] postNotificationName:ODOEditingContextObjectsWillBeDeletedNotification object:self userInfo:userInfo];
[userInfo release];
for (ODOObject *object in toDelete) {
[self _snapshotObjectForDeletion:object];
}
}
// Since we do delete propagation immediately, and since there is no other good point, we have an out NSError argument here for the results from -validateForDelete:.
- (BOOL)deleteObject:(ODOObject *)object error:(NSError **)outError;
{
ODOEditingContextAssertOwnership(self);
DEBUG_DELETE(@"DELETE: object:%@", [object shortDescription]);
OBINVARIANT([self _checkInvariants]);
OBPRECONDITION(!_isValidatingAndWritingChanges); // Can't make edits in the validation methods
OBPRECONDITION(!_isDeletingObjects);
OBPRECONDITION(object);
OBPRECONDITION([object editingContext] == self);
OBPRECONDITION([_registeredObjectByID objectForKey:[object objectID]] == object); // has to be registered
OBPRECONDITION(![_undoManager isUndoingOrRedoing]); // this public API shouldn't be called to undo/redo. Only to 'do'.
// Bail on objects that are already deleted or invalid instead of crashing. This can easily happen if UI code can select both a parent and child and delete them w/o knowing that the deletion of the parent will get the child too. Nice if the UI handles it, but shouldn't crash or do something crazy otherwise.
if (!object) {
DEBUG_DELETE(@"DELETE: given nil object");
return YES; // maybe return a user-cancelled error?
}
if (object.hasBeenDeletedOrInvalidated) {
DEBUG_DELETE(@"DELETE: %@ already invalid:%d deleted:%d hasStartedDeletion:%d hasFinishedDeletion:%d -- bailing", [object shortDescription], [object isInvalid], [object isDeleted], object->_flags.hasStartedDeletion, object->_flags.hasFinishedDeletion);
return YES; // maybe return a user-cancelled error?
}
if (_ODOObjectIsUndeletable(object)) {
// Whether this is right is debatable. Maybe we should do the deletion as normal with propagation nullifying the relationships. On the down side, that could result in no updates and just nullifications (but we have the problem of -prepareForDeletion doing edits when the deletion is rejected anyway...)
// Returning a user-cancelled error here since, unlike the the invalid/deleted case, we return with 'object' still being live.
DEBUG_DELETE(@"DELETE: undeletable -- bailing");
OBUserCancelledError(outError);
return NO;
}
OBASSERT(!object.hasBeenDeletedOrInvalidated);
OBASSERT([_processedDeletedObjects member:object] == nil); // can't be deleted already
OBASSERT([_recentlyDeletedObjects member:object] == nil); // or recently
// Inform the object being deleted. It can update itself or any related object, possibly to avoid delete propagation, so do this before tracing relationships.
[object prepareForDeletion];
// See below; we can't have any unprocessed inserts or updates. Any updates from the -prepareForDeletion above would be fine, but they'd confuse our assertions.
while (_recentlyInsertedObjects || _recentlyUpdatedObjects) {
DEBUG_DELETE(@"DELETE: processing pending changes...");
[self processPendingChanges];
}
OBASSERT(!_recentlyInsertedObjects);
OBASSERT(!_recentlyUpdatedObjects);
_isDeletingObjects = YES;
@try {
// We do delete propagation immediately rather than delaying it until -processPendingChanges. Not 100% sure what CoreData does. For now, only the externally initialized delete will go through public API. That is, subclasses won't get a -deleteObject: for propagated deletes.
// Trace the object graph figuring out what we need to cascade, nullify and deny. This operation should make NO changes in case there is an error detected.
TraceForDeletionContext ctx;
memset(&ctx, 0, sizeof(ctx));
ctx.self = self;
ctx.toDelete = [NSMutableSet set]; // Objects that have been cascaded
ctx.relationshipsToNullifyByObjectID = [NSMutableDictionary dictionary]; // objectID -> array of to-one relationship keys
ctx.denyObjectIDToReferer = [NSMutableDictionary dictionary];
ctx.error = nil;
_traceForDeletion(object, &ctx);
if (ctx.fail) {
if (outError != NULL)
*outError = ctx.error;
return NO;
}
DEBUG_DELETE(@"DELETE: toDelete: %@", [ctx.toDelete setByPerformingSelector:@selector(shortDescription)]);
DEBUG_DELETE(@"DELETE: relationshipsToNullifyByObjectID: %@", ctx.relationshipsToNullifyByObjectID);
DEBUG_DELETE(@"DELETE: denyObjectIDToReferer: %@", ctx.denyObjectIDToReferer);
// Before making any changes, check for deny. CoreData had deletions supercedeing deny. That is, if we have (not so hypoteticalliy) a one-to-one between Project and Task with Project->Task being cascade and Task->Project being deny, then if we start the delete at Project, we'll then cascade to Task and find a deny pointing back to Project. We'll make a note of this when tracing the object graph. But, since the Project is getting deleted, we'll ignore the deny. Thus, deny only applies if the object being denied isn't getting deleted.
if ([ctx.denyObjectIDToReferer count] > 0) {
CFSetApplyFunction((CFSetRef)ctx.toDelete, _removeDenyApplier, ctx.denyObjectIDToReferer);
// If there are still denies in place, log an error and bail
if ([ctx.denyObjectIDToReferer count] > 0) {
OBRequestConcreteImplementation(self, _cmd);
}
}
// Before nullifying relationships and marking the objects as deleted, post an early notification for observers that want to be notified before these changes.
[[NSNotificationCenter defaultCenter] postNotificationName:ODOEditingContextObjectsPreparingToBeDeletedNotification object:self userInfo:@{ODODeletedObjectsKey:ctx.toDelete}];
// Turns out none of our objects implement -validateForDelete: right now.
#if 0
// Validate deletion of all the objects that got collected. Note that the objects and their neighbors will be in their pre-deletion state.
// TODO: Need a general 'disallow edits' flag. -validateForDelete: should not add more edits.
OBASSERT([toDelete count] >= 1);
ValidateForDeleteApplierContext ctx;
memset(&ctx, 0, sizeof(ctx));
CFSetApplyFunction((CFSetRef)toDelete, _validateForDeleteApplier, &ctx);
if (ctx.failed) {
if (outError)
*outError = ctx.error;
return NO;
}
#endif
// We CANNOT have recent insertions or updates, as it turns out. If we do, then someone who has fetched against us, and gotten back a match due to in-memory updates of results sets, will be confused if we don't send a deletion notification. So, above, we've called -processPendingChanges to ensure that everything has been notified and flattened into the processed changes. After the _nullifyRelationships application, though, we will likely have recently updated objects.
OBASSERT(!_recentlyInsertedObjects);
OBASSERT(!_recentlyUpdatedObjects);
// Take a snapshot of this object, if needed, before nullifying relationships and deleting
[self _snapshotObjectPropertiesIfNeeded:object];
CFDictionaryApplyFunction((CFDictionaryRef)ctx.relationshipsToNullifyByObjectID, _nullifyRelationships, &ctx);
ODOEditingContextInternalDeleteObjects(self, ctx.toDelete);
OBINVARIANT([self _checkInvariants]);
} @finally {
_isDeletingObjects = NO;
}
return YES;
}
static void ODOEditingContextDidDeleteObjects(ODOEditingContext *self, NSSet *deleted)
{
// We used to also call _invalidate on deleted objects, but do not any longer to allow SwiftUI Views to access their values.
NSMutableDictionary *objectByID = self->_registeredObjectByID;
for (ODOObject *object in deleted) {
// Mark the object as having finished deletion. Property changes past this point will be ignored and produce an assertion failure.
OBASSERT(object->_flags.hasStartedDeletion);
OBASSERT(!object->_flags.hasFinishedDeletion);
object->_flags.hasFinishedDeletion = 1;
// Forget the deleted object.
ODOObjectID *objectID = [object objectID];
OBASSERT([objectByID objectForKey:objectID] == object);
[objectByID removeObjectForKey:objectID];
// Clear its backpointer to us. We used to get this from calling -_invalidate.
[object->_editingContext release];
object->_editingContext = nil;
// Clients should hear about the deletion viw KVO/notifications or the like and should have no reason to keep this object
OBExpectDeallocation(object);
}
}
static NSDictionary *_createChangeSetNotificationUserInfo(NSSet * _Nullable insertedObjects, NSSet * _Nullable updatedObjects, NSSet * _Nullable deletedObjects, NSDictionary <ODOObjectID *, ODOObjectSnapshot *> *committedPropertySnapshotByObjectID, NSDictionary <ODOObjectID *, ODOObjectSnapshot *> *lastProcessedPropertySnapshotByObjectID)
{
// Making copies of these sets since we mutate _recentlyUpdatedObjects below while merging (at least for the call from -_internal_processPendingChanges
NSMutableDictionary *userInfo = [[NSMutableDictionary alloc] init];
if (insertedObjects != nil) {
NSSet *set = [insertedObjects copy];
userInfo[ODOInsertedObjectsKey] = set;
[set release];
}
if (updatedObjects != nil) {
NSSet *set = [updatedObjects copy];
userInfo[ODOUpdatedObjectsKey] = set;
[set release];
// Build a subset of the objects that have material edits.
NSMapTable *materiallyUpdatedValues = nil;
for (ODOObject *object in updatedObjects) {
// Might be called for a recent update of a processed insert and -changedNonDerivedChangedValue currently does OBRequestConcreteImplementation() for inserted objects since its meaning is unclear in general. Here we'll contend that an 'insert' is a material update (even if no recent updates are material).
if ([object isInserted] || [object hasChangedNonDerivedChangedValue]) {
if (materiallyUpdatedValues == nil) {
materiallyUpdatedValues = [NSMapTable strongToStrongObjectsMapTable];
}
[materiallyUpdatedValues setObject:[object changedNonDerivedValues] forKey:object];
#if 0 && defined(DEBUG_bungi)
NSLog(@"material update to %@: %@", [object shortDescription], [object isInserted] ? (id)object : (id)[object changedValues]);
#endif
} else {
#if 0 && defined(DEBUG_bungi)
NSLog(@"dropping phantom update to %@; changes = %@", [object shortDescription], [object changedValues]);
#endif
}
}
if (materiallyUpdatedValues != nil) {
userInfo[ODOMateriallyUpdatedObjectPropertiesKey] = materiallyUpdatedValues;
NSSet *materialUpdates = [NSSet setByEnumerating:[materiallyUpdatedValues keyEnumerator]];
userInfo[ODOMateriallyUpdatedObjectsKey] = materialUpdates;
}
}
if (deletedObjects != nil) {
NSSet *set = [deletedObjects copy];
userInfo[ODODeletedObjectsKey] = set;
NSMutableDictionary *deletedSnapshots = [[NSMutableDictionary alloc] init];
for (ODOObject *deletedObject in set) {
ODOObjectID *deletedID = deletedObject.objectID;
ODOObjectSnapshot *snapshot = lastProcessedPropertySnapshotByObjectID[deletedID];
if (snapshot == nil) {
snapshot = committedPropertySnapshotByObjectID[deletedID];
}
deletedSnapshots[deletedID] = snapshot;
}
userInfo[ODODeletedObjectPropertySnapshotsKey] = deletedSnapshots;
[deletedSnapshots release];
[set release];
}
return userInfo;
}
// The 'processed' ivars have the sets of objects that have been registered in the undo manager and had change notifications posted regarding their state changes. Here we move recent changes to the processed state, logging undos and notifications. Returns YES if there were any recent changes, NO otherwise.
- (BOOL)_internal_processPendingChanges;
{
// NOTE: We can't delay delete propagation to here since OmniFocusModel depends on immediate delete propagation. -[OFMTreeObject _updateChildrenCounts] used to call -processPendingChanges to force delete propagation, but that could cause recursive calls to -processPendingChanges. Since we delete immediately, this isn't necessary in OmniDataObjects.
// TODO: Notify all the objects that are about to be processed (something that CoreData doesn't do). We can use this to calclate summarized values before the ODOEditingContextObjectsDidChangeNotification notification goes out to listeners that might want to read them.
// TODO: Handle the case where an object is inserted, processed, updated, deleted. That is -deleteObject: should prune objects from the recent updates so that -isUpdated and -updatedObjects don't have to consider that (and we don't need/want the undo/notification to have an object in both the updated and deleted sets).
// Send notifications for inserts, updates and deletes based on the pending edits (i.e., a previously inserted object can be the subject of a update notification and a previous insert/update can be the subject of a delete).
NSDictionary *userInfo = _createChangeSetNotificationUserInfo(_recentlyInsertedObjects, _recentlyUpdatedObjects, _recentlyDeletedObjects, _objectIDToCommittedPropertySnapshot, _objectIDToLastProcessedSnapshot);
NSNotification *notification = [NSNotification notificationWithName:ODOEditingContextObjectsDidChangeNotification object:self userInfo:userInfo];
[userInfo release];
// Register undos based on the recent changes, if we have an undo manager, along with any snapshots necessary to get back into the right state after undoing.
// TODO: Record only the object IDs and snapshots?
// TODO: These snapshots aren't right -- they are from the last *save* but we need snapshots from the last -processPendingChanges.
if (_undoManager != nil) {
[self _registerUndoForRecentChanges];
}
//
// Merge the recent changes into the processed changes.
//
// Our recent snapshots can be thrown away (any time after the undo is logged really). In fact, maybe we shouldn't keep this if we don't have an undo manager/on iPhone.
[_objectIDToLastProcessedSnapshot release];
_objectIDToLastProcessedSnapshot = nil;
// Any updates that are to processed inserts (i.e., an object was inserted, changes processed and then updated) are irrelevant as far as -save: is concerned (though undo and notifications care above).
[_recentlyUpdatedObjects minusSet:_processedInsertedObjects];
// Any previously processed inserts or updates that have recently been deleted are also now irrelevant for -save:.
if (_recentlyDeletedObjects != nil) {
// Also, any processed inserts are irrelevant for -save:. That is, the processed insert and recent delete cancel out.
// TODO: We don't actually allow re-inserts and should clean out lingering support for it.
// However, if the processed insert was actual a re-insert, the delete does not cancel it out; we must preserve the delete as a material delete.
if ([_processedInsertedObjects intersectsSet:_recentlyDeletedObjects]) {
// Anything that was inserted, but not reinserted can just be cancelled; a material delete is not required
NSMutableSet *cancelledInserts = [[NSMutableSet alloc] initWithSet:_recentlyDeletedObjects];
[cancelledInserts intersectSet:_processedInsertedObjects];
[cancelledInserts minusSet:_reinsertedObjects];