Class:OneToManyMapping - Superclass: AssociationMapping AssociationMapping
⌊ OneToManyMapping
public class OneToManyMapping
extends AssociationMapping
Field Summary | |
---|---|
mixed | READ-ONLY: Order this collection by the given SQL snippet. |
boolean | READ-ONLY: Whether to delete orphaned elements (removed from the collection) |
Fields inherited from Doctrine\ORM\Mapping\AssociationMapping | |
---|---|
FETCH_EAGER, FETCH_LAZY, declared, fetchMode, inherited, inversedBy, isCascadeDetach, isCascadeMerge, isCascadePersist, isCascadeRefresh, isCascadeRemove, isOwningSide, joinTable, mappedBy, sourceEntityName, sourceFieldName, targetEntityName |
Method Summary | |
---|---|
boolean | {@inheritdoc} |
void | load(object sourceEntity, mixed targetCollection, EntityManager em, array joinColumnValues, $em The, $joinColumnValues , object target) Loads a one-to-many collection. |
boolean | Whether orphaned elements (removed from the collection) should be deleted. |
Methods inherited from Doctrine\ORM\Mapping\AssociationMapping | |
---|---|
getQuotedJoinTableName, hasCascades, isEagerlyFetched, isLazilyFetched, isManyToMany, isOneToMany, isOneToOne, load, usesJoinTable |
public mixed $orderBy
READ-ONLY: Order this collection by the given SQL snippet.
public boolean $orphanRemoval = false
READ-ONLY: Whether to delete orphaned elements (removed from the collection)
public boolean isOneToMany()
public void load(object sourceEntity, mixed targetCollection, EntityManager em, array joinColumnValues, $em The, $joinColumnValues , object target)
Loads a one-to-many collection.
public boolean shouldDeleteOrphans()
Whether orphaned elements (removed from the collection) should be deleted.
Represents a one-to-many mapping.
NOTE: One-to-many mappings can currently not be uni-directional (one -> many). They must either be bidirectional (one <-> many) or unidirectional (many -> one). In other words, the many-side MUST be the owning side and the one-side MUST be the inverse side.
IMPORTANT NOTE:
The fields of this class are only public for 2 reasons: 1) To allow fast READ access. 2) To drastically reduce the size of a serialized instance (private/protected members get the whole class name, namespace inclusive, prepended to every property in the serialized representation).
Instances of this class are stored serialized in the metadata cache together with the owning ClassMetadata instance.