CKRecordZone
A database partition that contains related records.
Declaration
class CKRecordZoneOverview
Zones are an important part of how you organize your data. The public and private databases each have a single default zone. In the private database, you can use CKRecordZone objects to create additional custom zones as necessary. Use custom zones to arrange and encapsulate groups of related records in the private database. Custom zones support other capabilities too, such as the ability to write multiple records as a single atomic transaction.
Treat each custom zone as a single unit of data that is separate from every other zone in the database. You can add records inside the zone. You can also create links between the records inside a zone by using the CKRecord.Reference class. However, the CKRecord.Reference class doesn’t support cross-zone linking, so each reference object must point to a record in the same zone as the current record.
Use the CKRecordZone class as-is and don’t subclass it.
Creating a Custom Record Zone
Generally, you use instances of this class to create and manage custom zones. Although you can use this class to retrieve a database’s default zone, most operations act on records in the default zone by default, so you rarely need to specify it explicitly.
To create a custom zone, use CKRecordZone to create the zone object, and then save that zone to the user’s private database using a CKModifyRecordZonesOperation object. You can’t save any records in the zone until you save it to the database. When creating records, explicitly specify the zone ID if you want the records to reside in a specific zone; otherwise, they save to the default zone. You can’t create custom zones in a public database.
After creating a CKRecordZone object and saving it to the database, you don’t interact with the object much. Instead, most interactions occur with its corresponding CKRecordZone.ID object, which you use to refer to the zone when creating records.