dontwatchmyprofile - Page 3

Does Core Data take appropriate action automatically when there's a Low Memory Warning?

- by dontWatchMyProfile

Does it turn some managed objects into faults when there's a Low Memory Warning? Or must we do that manually by calling the -refreshObjects:mergeChanges: method which puts the affected managed objects on diet quickly? And...would that actually hurt? What if these objects are currently used by an NSFetchedResultsController to show up on a table view?

Read the article

Is there any difference in the implementation of these three validation methods?

- by dontWatchMyProfile

Core Data is calling these methods in certain situations: - (BOOL)validateForInsert:(NSError **)outError; - (BOOL)validateForUpdate:(NSError **)outError; - (BOOL)validateForDelete:(NSError **)outError; I wonder if they're doing anything different, or if they're essentially doing the exact same things. As far as I know, these methods call the -validateValue:forKey:error: method once for every property. The only difference I can imagine is in the .validateForDelete: method. I see no reason why to validate an object when it shall be deleted, except for applying delete rules, probably only in the case of the DENY rule.

Read the article

Does this collection operator method also work on the iPhone?

- by dontWatchMyProfile

NSNumber *salaryOverhead = [anEmployee valueForKeyPath:@"[email protected]"];

Read the article

How to align an 90 deg rotated label perfectly with the pixels?

- by dontWatchMyProfile

When rotating a label, the text is rendered very ugly. Is there an convenient way to get the label aligned with the pixels? Maybe there is some way of rounding the transform of the view, so that it isn't misaligned?

Read the article

What's -mutableSetValueForKey: returning, actually? Is that something special?

- by dontWatchMyProfile

From the docs: You usually access to-many relationships using mutableSetValueForKey:, which returns a proxy object that both mutates the relationship and sends appropriate key-value observing notifications for you. So this returns an "intelligent" NSMutableSet which automatically lets the context delete objects when they get deleted from the set, and reverse? Is that a proxy object?

Read the article

What happens when a fault is "fired"?

- by dontWatchMyProfile

What happens when a fault is "fired"?

Read the article

What's the staleness interval good for?

- by dontWatchMyProfile

When should I care about the staleness interval in Core Data?

Read the article

What's the consequence when Core Data detects an optimistic locking failure when trying to save?

- by dontWatchMyProfile

I get it: When a managed object context saves, the snapshots of all edited objects are compared against the values in the persistent store to see if the PS has changed since the snapshot was made. If it did change, then there's a conflict and optimistic locking failed, according to Apple. But now, what's the consequence of this? What happens next? What are my options in this case?

Read the article

Which one should I prefer for relasing my custom non-managed properties?

- by dontWatchMyProfile

-willTurnIntoFault or -didTurnIntoFault? I guess it's stupid to release properties in both of them, so I must choose one. Which is the best?

Read the article

How does Undo work?

- by dontWatchMyProfile

How does undo work? Does it copy all the managed objects every time any of the values change? Or does it only copy the actual changes together with an information which objects were affected? Is that heavy or lightweight?

Developer IT