Hey folks.
Nick mentions that we "might" need to initialize Schema in order to use a public database. The only examples I've seen on this is to create an options, and then call 'options.shouldInitializeSchema = true'. The problem I'm seeing is that the options class doesn't have such a parameter. "NSPersistentCloudKitContainerOptions" only has a containerIdentifier and a databaseScope and an init.
If that's correct, then I'm not sure I understand how to initialize the scheme. Obviously, I can just create a record in CoreData and wait for the PersistentContainer to mirror the schema up to CloudKit and then add the needed indexes, but I assume there's a need to initialize, or else Nick wouldn't have mentioned it.
Any insights would be appreciated.
Thanks
Steve
Nick mentions that we "might" need to initialize Schema in order to use a public database. The only examples I've seen on this is to create an options, and then call 'options.shouldInitializeSchema = true'. The problem I'm seeing is that the options class doesn't have such a parameter. "NSPersistentCloudKitContainerOptions" only has a containerIdentifier and a databaseScope and an init.
If that's correct, then I'm not sure I understand how to initialize the scheme. Obviously, I can just create a record in CoreData and wait for the PersistentContainer to mirror the schema up to CloudKit and then add the needed indexes, but I assume there's a need to initialize, or else Nick wouldn't have mentioned it.
Any insights would be appreciated.
Thanks
Steve
