ToManyUnordered
public final class ToManyUnordered<D> : ToManyRelationshipKeyPathStringConvertible, RelationshipProtocol where D : CoreStoreObject
extension RelationshipContainer.ToManyUnordered: Sequence
The containing type for to-many unordered relationships. Any CoreStoreObject subclass can be a destination type. Inverse relationships should be declared from the destination type as well, using the inverse: argument for the relationship.
class Dog: CoreStoreObject {
let master = Relationship.ToOne<Person>("master")
}
class Person: CoreStoreObject {
let pets = Relationship.ToManyUnordered<Dog>("pets", inverse: { $0.master })
}
Important
Relationship.ToManyUnordered properties are required to be stored properties. Computed properties will be ignored, including lazy and weak properties.
-
Initializes the metadata for the relationship. All relationships require an “inverse”, so updates to to this object’s relationship are also reflected on its destination object. Make sure to declare this relationship’s inverse relationship on its destination object. Due to Swift’s compiler limitation, only one of the relationship and its inverse can declare an
inverse:argument.class Dog: CoreStoreObject { let master = Relationship.ToOne<Person>("master") } class Person: CoreStoreObject { let pets = Relationship.ToManyOrdered<Dog>("pets", inverse: { $0.master }) }Declaration
Swift
public convenience init( _ keyPath: KeyPathString, deleteRule: DeleteRule = .nullify, minCount: Int = 0, maxCount: Int = 0, versionHashModifier: @autoclosure @escaping () -> String? = nil, renamingIdentifier: @autoclosure @escaping () -> String? = nil, affectedByKeyPaths: @autoclosure @escaping () -> Set<String> = [])Parameters
keyPaththe permanent name for this relationship.
minCountthe minimum number of objects in this relationship UNLESS THE RELATIONSHIP IS EMPTY. This means there might be zero objects in the relationship, which might be less than
minCount. If the number of objects in the relationship do not satisfyminCountandmaxCount, the transaction’s commit (or auto-commit) would fail with a validation error.maxCountthe maximum number of objects in this relationship. If the number of objects in the relationship do not satisfy
minCountandmaxCount, the transaction’s commit (or auto-commit) would fail with a validation error.inversethe inverse relationship that is declared for the destination object. All relationships require an “inverse”, so updates to to this object’s relationship are also reflected on its destination object.
deleteRuledefines what happens to relationship when an object is deleted. Valid values are
.nullify,.cascade, and.delete. Defaults to.nullify.versionHashModifierused to mark or denote a relationship as being a different “version” than another even if all of the values which affect persistence are equal. (Such a difference is important in cases where the properties are unchanged but the format or content of its data are changed.)
renamingIdentifierused to resolve naming conflicts between models. When creating an entity mapping between entities in two managed object models, a source entity property and a destination entity property that share the same identifier indicate that a property mapping should be configured to migrate from the source to the destination. If unset, the identifier will be the property’s name.
affectedByKeyPathsa set of key paths for properties whose values affect the value of the receiver. This is similar to
NSManagedObject.keyPathsForValuesAffectingValue(forKey:). -
init(_:inverse: deleteRule: minCount: maxCount: versionHashModifier: renamingIdentifier: affectedByKeyPaths: ) Initializes the metadata for the relationship. All relationships require an “inverse”, so updates to to this object’s relationship are also reflected on its destination object. Make sure to declare this relationship’s inverse relationship on its destination object. Due to Swift’s compiler limitation, only one of the relationship and its inverse can declare an
inverse:argument.class Dog: CoreStoreObject { let master = Relationship.ToOne<Person>("master") } class Person: CoreStoreObject { let pets = Relationship.ToManyOrdered<Dog>("pets", inverse: { $0.master }) }Declaration
Swift
public convenience init( _ keyPath: KeyPathString, inverse: @escaping (D) -> RelationshipContainer<D>.ToOne<O>, deleteRule: DeleteRule = .nullify, minCount: Int = 0, maxCount: Int = 0, versionHashModifier: @autoclosure @escaping () -> String? = nil, renamingIdentifier: @autoclosure @escaping () -> String? = nil, affectedByKeyPaths: @autoclosure @escaping () -> Set<String> = [])Parameters
keyPaththe permanent name for this relationship.
minCountthe minimum number of objects in this relationship UNLESS THE RELATIONSHIP IS EMPTY. This means there might be zero objects in the relationship, which might be less than
minCount. If the number of objects in the relationship do not satisfyminCountandmaxCount, the transaction’s commit (or auto-commit) would fail with a validation error.maxCountthe maximum number of objects in this relationship. If the number of objects in the relationship do not satisfy
minCountandmaxCount, the transaction’s commit (or auto-commit) would fail with a validation error.inversethe inverse relationship that is declared for the destination object. All relationships require an “inverse”, so updates to to this object’s relationship are also reflected on its destination object.
deleteRuledefines what happens to relationship when an object is deleted. Valid values are
.nullify,.cascade, and.delete. Defaults to.nullify.versionHashModifierused to mark or denote a relationship as being a different “version” than another even if all of the values which affect persistence are equal. (Such a difference is important in cases where the properties are unchanged but the format or content of its data are changed.)
renamingIdentifierused to resolve naming conflicts between models. When creating an entity mapping between entities in two managed object models, a source entity property and a destination entity property that share the same identifier indicate that a property mapping should be configured to migrate from the source to the destination. If unset, the identifier will be the property’s name.
affectedByKeyPathsa set of key paths for properties whose values affect the value of the receiver. This is similar to
NSManagedObject.keyPathsForValuesAffectingValue(forKey:). -
init(_:inverse: deleteRule: minCount: maxCount: versionHashModifier: renamingIdentifier: affectedByKeyPaths: ) Initializes the metadata for the relationship. All relationships require an “inverse”, so updates to to this object’s relationship are also reflected on its destination object. Make sure to declare this relationship’s inverse relationship on its destination object. Due to Swift’s compiler limitation, only one of the relationship and its inverse can declare an
inverse:argument.class Dog: CoreStoreObject { let master = Relationship.ToOne<Person>("master") } class Person: CoreStoreObject { let pets = Relationship.ToManyOrdered<Dog>("pets", inverse: { $0.master }) }Declaration
Swift
public convenience init( _ keyPath: KeyPathString, inverse: @escaping (D) -> RelationshipContainer<D>.ToManyOrdered<O>, deleteRule: DeleteRule = .nullify, minCount: Int = 0, maxCount: Int = 0, versionHashModifier: @autoclosure @escaping () -> String? = nil, renamingIdentifier: @autoclosure @escaping () -> String? = nil, affectedByKeyPaths: @autoclosure @escaping () -> Set<String> = [])Parameters
keyPaththe permanent name for this relationship.
minCountthe minimum number of objects in this relationship UNLESS THE RELATIONSHIP IS EMPTY. This means there might be zero objects in the relationship, which might be less than
minCount. If the number of objects in the relationship do not satisfyminCountandmaxCount, the transaction’s commit (or auto-commit) would fail with a validation error.maxCountthe maximum number of objects in this relationship. If the number of objects in the relationship do not satisfy
minCountandmaxCount, the transaction’s commit (or auto-commit) would fail with a validation error.inversethe inverse relationship that is declared for the destination object. All relationships require an “inverse”, so updates to to this object’s relationship are also reflected on its destination object.
deleteRuledefines what happens to relationship when an object is deleted. Valid values are
.nullify,.cascade, and.delete. Defaults to.nullify.versionHashModifierused to mark or denote a relationship as being a different “version” than another even if all of the values which affect persistence are equal. (Such a difference is important in cases where the properties are unchanged but the format or content of its data are changed.)
renamingIdentifierused to resolve naming conflicts between models. When creating an entity mapping between entities in two managed object models, a source entity property and a destination entity property that share the same identifier indicate that a property mapping should be configured to migrate from the source to the destination. If unset, the identifier will be the property’s name.
affectedByKeyPathsa set of key paths for properties whose values affect the value of the receiver. This is similar to
NSManagedObject.keyPathsForValuesAffectingValue(forKey:). -
init(_:inverse: deleteRule: minCount: maxCount: versionHashModifier: renamingIdentifier: affectedByKeyPaths: ) Initializes the metadata for the relationship. All relationships require an “inverse”, so updates to to this object’s relationship are also reflected on its destination object. Make sure to declare this relationship’s inverse relationship on its destination object. Due to Swift’s compiler limitation, only one of the relationship and its inverse can declare an
inverse:argument.class Dog: CoreStoreObject { let master = Relationship.ToOne<Person>("master") } class Person: CoreStoreObject { let pets = Relationship.ToManyOrdered<Dog>("pets", inverse: { $0.master }) }Declaration
Swift
public convenience init( _ keyPath: KeyPathString, inverse: @escaping (D) -> RelationshipContainer<D>.ToManyUnordered<O>, deleteRule: DeleteRule = .nullify, minCount: Int = 0, maxCount: Int = 0, versionHashModifier: @autoclosure @escaping () -> String? = nil, renamingIdentifier: @autoclosure @escaping () -> String? = nil, affectedByKeyPaths: @autoclosure @escaping () -> Set<String> = [])Parameters
keyPaththe permanent name for this relationship.
minCountthe minimum number of objects in this relationship UNLESS THE RELATIONSHIP IS EMPTY. This means there might be zero objects in the relationship, which might be less than
minCount. If the number of objects in the relationship do not satisfyminCountandmaxCount, the transaction’s commit (or auto-commit) would fail with a validation error.maxCountthe maximum number of objects in this relationship. If the number of objects in the relationship do not satisfy
minCountandmaxCount, the transaction’s commit (or auto-commit) would fail with a validation error.inversethe inverse relationship that is declared for the destination object. All relationships require an “inverse”, so updates to to this object’s relationship are also reflected on its destination object.
deleteRuledefines what happens to relationship when an object is deleted. Valid values are
.nullify,.cascade, and.delete. Defaults to.nullify.versionHashModifierused to mark or denote a relationship as being a different “version” than another even if all of the values which affect persistence are equal. (Such a difference is important in cases where the properties are unchanged but the format or content of its data are changed.)
renamingIdentifierused to resolve naming conflicts between models. When creating an entity mapping between entities in two managed object models, a source entity property and a destination entity property that share the same identifier indicate that a property mapping should be configured to migrate from the source to the destination. If unset, the identifier will be the property’s name.
affectedByKeyPathsa set of key paths for properties whose values affect the value of the receiver. This is similar to
NSManagedObject.keyPathsForValuesAffectingValue(forKey:). -
The relationship value
Declaration
Swift
public var value: ReturnValueType { get set }
-
Declaration
Swift
public var cs_keyPathString: String { get }
-
Declaration
Swift
public typealias ObjectType = O -
Declaration
Swift
public typealias DestinationValueType = D
-
Declaration
Swift
public typealias ReturnValueType = Set<DestinationValueType>
-
Observes changes in the receiver value. When the returned
CoreStoreObjectKeyValueObservationis deinited or invalidated, it will stop observing.Declaration
Swift
public func observe(options: NSKeyValueObservingOptions = [], changeHandler: @escaping (O, CoreStoreObjectUnorderedDiff<D>) -> Void) -> CoreStoreObjectKeyValueObservationParameters
optionsThe flags indicating which values to include in the change dictionary.
-
The number of elements in the set.
Declaration
Swift
public var count: Int { get } -
A Boolean value indicating whether the range contains no elements.
Declaration
Swift
public var isEmpty: Bool { get }
-
Declaration
Swift
public typealias Iterator = AnyIterator<D> -
Declaration
Swift
public func makeIterator() -> Iterator
-
Assigns a sequence of objects to the relationship. The operation
person.pets .= [dog, cat]is equivalent to
person.pets.value = [dog, cat]Declaration
Swift
public static func .= <S>(relationship: RelationshipContainer<O>.ToManyUnordered<D>, newValue: S) where D == S.Element, S : Sequence -
Assigns a sequence of objects to the relationship. The operation
person.pets .= anotherPerson.petsis equivalent to
person.pets.value = anotherPerson.pets.valueDeclaration
Swift
public static func .= <O2>(relationship: RelationshipContainer<O>.ToManyUnordered<D>, relationship2: RelationshipContainer<O2>.ToManyUnordered<D>) where O2 : CoreStoreObject -
Assigns a sequence of objects to the relationship. The operation
person.pets .= anotherPerson.petsis equivalent to
person.pets.value = anotherPerson.pets.valueDeclaration
Swift
public static func .= <O2>(relationship: RelationshipContainer<O>.ToManyUnordered<D>, relationship2: RelationshipContainer<O2>.ToManyOrdered<D>) where O2 : CoreStoreObject -
Compares the if the relationship’s objects and a set of objects have the same elements.
if person.pets .== Set<Animal>([dog, cat]) { ... }is equivalent to
if person.pets.value == Set<Animal>([dog, cat]) { ... }Declaration
Swift
public static func .== (relationship: RelationshipContainer<O>.ToManyUnordered<D>, set: Set<D>) -> Bool -
Compares if a set of objects and a relationship’s objects have the same elements.
if Set<Animal>([dog, cat]) .== person.pets { ... }is equivalent to
if Set<Animal>([dog, cat]) == person.pets.value { ... }Declaration
Swift
public static func .== (set: Set<D>, relationship: RelationshipContainer<O>.ToManyUnordered<D>) -> Bool -
Compares if a relationship’s objects and another relationship’s objects have the same elements.
if person.pets .== anotherPerson.pets { ... }is equivalent to
if person.pets.value == anotherPerson.pets.value { ... }Declaration
Swift
public static func .== <O2>(relationship: RelationshipContainer<O>.ToManyUnordered<D>, relationship2: RelationshipContainer<O2>.ToManyUnordered<D>) -> Bool where O2 : CoreStoreObject
View on GitHub
ToManyUnordered Class Reference