我们的每个数据行都包含一个唯一的 uuid
列。
以前,在采用CloudKit之前, uuid
列具有唯一的约束。这使我们能够防止数据重复。
现在,我们开始将CloudKit集成到现有的Coredata中。这种独特的约束被删除。以下用户流将导致数据重复。
使用CloudKit时引起数据重复的步骤
- 首次
- 。由于有空数据,因此生成了具有预定义
uuid
的预定义数据。
- 预定义的数据与iCloud同步。
- 该应用程序已卸载。
- 该应用程序已重新安装。
- 首次启动该应用程序。
- 由于有空数据,因此生成了具有预定义
uuid
的预定义数据。
- 步骤3的先前旧的预定义数据是与设备同步的。
- 现在,我们有2个具有相同
uuid
的预定义数据! :(
我想知道,我们是否有办法防止这种重复?
在第8步中,我们希望我们有一种执行此类逻辑的方法
检查Coredata中是否存在此类UUID。如果没有,请写信给Coredata。
如果没有,我们将选择具有最新更新日期的一个,然后覆盖
现有数据。
我曾经尝试将上述逻辑插入。为了防止保存,我正在使用 self.managedObjectContext?.rollback()
。但这只是崩溃了。
您有什么想法,我可以使用哪些可靠的机制,以防止Coredata CloudKit中的数据重复?
附加信息:
在采用CloudKit之前,
我们使用以下核心堆栈,
class CoreDataStack {
static let INSTANCE = CoreDataStack()
private init() {
}
private(set) lazy var persistentContainer: NSPersistentContainer = {
precondition(Thread.isMainThread)
let container = NSPersistentContainer(name: "xxx", managedObjectModel: NSManagedObjectModel.wenote)
container.loadPersistentStores(completionHandler: { (storeDescription, error) in
if let error = error as NSError? {
// This is a serious fatal error. We will just simply terminate the app, rather than using error_log.
fatalError("Unresolved error \(error), \(error.userInfo)")
}
})
// So that when backgroundContext write to persistent store, container.viewContext will retrieve update from
// persistent store.
container.viewContext.automaticallyMergesChangesFromParent = true
// TODO: Not sure these are required...
//
//container.viewContext.mergePolicy = NSMergeByPropertyObjectTrumpMergePolicy
//container.viewContext.undoManager = nil
//container.viewContext.shouldDeleteInaccessibleFaults = true
return container
}()
我们的CoreData Data Schema具有
- 独特的状态约束。
- 否认关系的删除规则。
- 对于非null字段没有默认值。
在采用CloudKit之后,
class CoreDataStack {
static let INSTANCE = CoreDataStack()
private init() {
}
private(set) lazy var persistentContainer: NSPersistentContainer = {
precondition(Thread.isMainThread)
let container = NSPersistentCloudKitContainer(name: "xxx", managedObjectModel: NSManagedObjectModel.wenote)
container.loadPersistentStores(completionHandler: { (storeDescription, error) in
if let error = error as NSError? {
// This is a serious fatal error. We will just simply terminate the app, rather than using error_log.
fatalError("Unresolved error \(error), \(error.userInfo)")
}
})
// So that when backgroundContext write to persistent store, container.viewContext will retrieve update from
// persistent store.
container.viewContext.automaticallyMergesChangesFromParent = true
// TODO: Not sure these are required...
//
//container.viewContext.mergePolicy = NSMergeByPropertyObjectTrumpMergePolicy
//container.viewContext.undoManager = nil
//container.viewContext.shouldDeleteInaccessibleFaults = true
return container
}()
我们将Coredata数据模式更改为
- 没有唯一的约束。
- 无效的关系删除规则。
- 具有非NULL字段的默认值。
基于开发人员技术支持工程师的反馈,来自 https://developer.apple。 forums/thread/699634吗
- com
- ?
/ 提供的被打破了。
Every of our data row, contains an unique uuid
column.
Previously, before adopting CloudKit, the uuid
column has a unique constraint. This enables us to prevent data duplication.
Now, we start to integrate CloudKit, into our existing CoreData. Such unique constraint is removed. The following user flow, will cause data duplication.
Steps to cause data duplication when using CloudKit
- Launch the app for the first time.
- Since there is empty data, a pre-defined data with pre-defined
uuid
is generated.
- The pre-defined data is sync to iCloud.
- The app is uninstalled.
- The app is re-installed.
- Launch the app for the first time.
- Since there is empty data, a pre-defined data with pre-defined
uuid
is generated.
- Previous old pre-defined data from step 3, is sync to the device.
- We are now having 2 pre-defined data with same
uuid
! :(
I was wondering, is there a way for us to prevent such duplication?
In step 8, we wish we have a way to execute such logic before written into CoreData
Check whether such uuid exists in CoreData. If not, write to CoreData.
If not, we will pick the one with latest update date, then overwrite
the existing data.
I once try to insert the above logic into https://developer.apple.com/documentation/coredata/nsmanagedobject/1506209-willsave . To prevent save, I am using self.managedObjectContext?.rollback()
. But it just crash.
Do you have any idea, what are some reliable mechanism I can use, to prevent data duplication in CoreData CloudKit?
Additional info:
Before adopting CloudKit
We are using using the following CoreData stack
class CoreDataStack {
static let INSTANCE = CoreDataStack()
private init() {
}
private(set) lazy var persistentContainer: NSPersistentContainer = {
precondition(Thread.isMainThread)
let container = NSPersistentContainer(name: "xxx", managedObjectModel: NSManagedObjectModel.wenote)
container.loadPersistentStores(completionHandler: { (storeDescription, error) in
if let error = error as NSError? {
// This is a serious fatal error. We will just simply terminate the app, rather than using error_log.
fatalError("Unresolved error \(error), \(error.userInfo)")
}
})
// So that when backgroundContext write to persistent store, container.viewContext will retrieve update from
// persistent store.
container.viewContext.automaticallyMergesChangesFromParent = true
// TODO: Not sure these are required...
//
//container.viewContext.mergePolicy = NSMergeByPropertyObjectTrumpMergePolicy
//container.viewContext.undoManager = nil
//container.viewContext.shouldDeleteInaccessibleFaults = true
return container
}()
Our CoreData data schema has
- Unique constraint.
- Deny deletion rule for relationship.
- Not having default value for non-null field.
After adopting CloudKit
class CoreDataStack {
static let INSTANCE = CoreDataStack()
private init() {
}
private(set) lazy var persistentContainer: NSPersistentContainer = {
precondition(Thread.isMainThread)
let container = NSPersistentCloudKitContainer(name: "xxx", managedObjectModel: NSManagedObjectModel.wenote)
container.loadPersistentStores(completionHandler: { (storeDescription, error) in
if let error = error as NSError? {
// This is a serious fatal error. We will just simply terminate the app, rather than using error_log.
fatalError("Unresolved error \(error), \(error.userInfo)")
}
})
// So that when backgroundContext write to persistent store, container.viewContext will retrieve update from
// persistent store.
container.viewContext.automaticallyMergesChangesFromParent = true
// TODO: Not sure these are required...
//
//container.viewContext.mergePolicy = NSMergeByPropertyObjectTrumpMergePolicy
//container.viewContext.undoManager = nil
//container.viewContext.shouldDeleteInaccessibleFaults = true
return container
}()
We change the CoreData data schema to
- Not having unique constraint.
- Nullify deletion rule for relationship.
- Having default value for non-null field.
Based on a feedback of a Developer Technical Support engineer from https://developer.apple.com/forums/thread/699634?login=true , hen mentioned we can
- Detecting Relevant Changes by Consuming Store Persistent History
- Removing Duplicate Data
But, it isn't entirely clear on how it should be implemented, as the github link provided is broken.
发布评论
评论(1)
一旦我们与CloudKit集成,就没有没有唯一的约束。
这一限制的解决方法是
当CloudKit执行插入?执行插入时,我们如何通知这种解决方法的挑战性部分,
这是在CloudKit执行插入时如何被通知的分步。
nspersistestoneThistoryTrackingKey
功能。nspersistentStorStoreMoteChangEnotification -Postoptionkey
功能。ViewContext.TransactionAuthor =“ App”
。这是一个重要的步骤,因此当我们查询交易历史记录时,我们知道我们的应用程序启动了哪个DB事务,以及CloudKit启动哪个DB事务。nspersistentStorStoreMoteChangeNotification -Postoptionkey
功能自动通知我们时,我们将开始查询交易历史记录。查询将根据交易作者和上次查询令牌过滤。请参阅代码示例以获取更多详细信息。代码示例
参考
coredatastack.swift
说明了一个类似的示例,有关如何在云同步之后删除重复的数据。There is no unique constraint feature once we have integrated with CloudKit.
The workaround on this limitation is
The challenging part of this workaround is, how can we be notified when there is insertion performed by CloudKit?
Here's step-by-step on how to be notified when there is insertion performed by CloudKit.
NSPersistentHistoryTrackingKey
feature in CoreData.NSPersistentStoreRemoteChangeNotificationPostOptionKey
feature in CoreData.viewContext.transactionAuthor = "app"
. This is an important step so that when we query on transaction history, we know which DB transaction is initiated by our app, and which DB transaction is initiated by CloudKit.NSPersistentStoreRemoteChangeNotificationPostOptionKey
feature, we will start to query on transaction history. The query will filter based on transaction author and last query token. Please refer to the code example for more detailed.Code example
Reference
CoreDataStack.swift
illustrate a similar example, on how to remove duplicated data after cloud sync.