Workaround CoreData's bug when using NSFetchRequest's affectedStores property

This commit is contained in:
John Rommel Estropia
2016-04-01 01:22:16 +09:00
parent 633ab0a249
commit 0b24072259
4 changed files with 26 additions and 10 deletions

View File

@@ -991,7 +991,7 @@ public final class ListMonitor<T: NSManagedObject> {
private init(context: NSManagedObjectContext, transactionQueue: GCDQueue, from: From<T>, sectionBy: SectionBy?, fetchClauses: [FetchClause], createAsynchronously: ((ListMonitor<T>) -> Void)?) {
let fetchRequest = NSFetchRequest()
let fetchRequest = CoreStoreFetchRequest()
fetchRequest.fetchLimit = 0
fetchRequest.resultType = .ManagedObjectResultType
fetchRequest.fetchBatchSize = 20

View File

@@ -175,7 +175,7 @@ public final class ObjectMonitor<T: NSManagedObject> {
private init(context: NSManagedObjectContext, object: T) {
let fetchRequest = NSFetchRequest()
let fetchRequest = CoreStoreFetchRequest()
fetchRequest.entity = object.entity
fetchRequest.fetchLimit = 0
fetchRequest.resultType = .ManagedObjectResultType