Orm provides very efficient way to work with entity relationships. Orm recognizes 4 types of relationship:
Use a relationship modifier to define relationship property. Modifiers
require to define a target entity, some modifiers need to be defined on the both
sides, then the reverse property definition is compulsory. If you want to define
only one-sided relationship, use oneSided=true
parameter. Other
parameters are optional: ordering, setting a cascade, or making the current side
primary (persisting is driven by the primary side). At least one side of
m:m
or 1:1
has to be defined as the primary.
Relationships do not support getters and setters as other entity properties.
{1:1 EntityName::$reversePropertyName}
{m:1 EntityName::$reversePropertyName}
{1:m EntityName::$reversePropertyName, orderBy=property}
{m:m EntityName::$reversePropertyName, isMain=true, orderBy=[property=DESC, anotherProperty=ASC]}
1:m
and m:m
relationships can define
collection's default ordering by orderBy
property. You may provide
either a property name, or an associated array where the key is a property
expression and the value is an ordering direction.
The property mapping into an actual column name may differ depending on the conventions. By default, Orm strips “id” suffixes when the column contains an foreign key reference.
All relationships can have defined a cascade behavior. Cascade behavior
defines if entity peristance or removal should affect other connected entities.
By default, all relationships have cascade for persist
. To define
cascade use an array of keywords: persist
and remove
.
Cascade works for every type of relationship.
// persist cascade is the default
{relModifier EntityName::$reversePropertyName} // equals to
{relModifier EntityName::$reversePropertyName, cascade=[persist]}
// adding remove cascade; you have to redefine persist cascade
{relModifier EntityName::$reversePropertyName, cascade=[persist, remove]}
// to disable persist cascade, provide empty cascade definition
{relModifier EntityName::$reversePropertyName, cascade=[]}
The persist and remove methods process entity with its cascade. You can turn off by the second optional method argument:
$usersRepository->persist($user, false);
$usersRepository->remove($user, false);
use Nextras\Orm\Relationships\OneHasMany;
/**
* @property int $id {primary}
* @property OneHasMany|Book[] $books {1:m Book::$author}
* @property OneHasMany|Book[] $translatedBooks {1:m Book::$translator}
*/
class Author extends Nextras\Orm\Entity\Entity
{}
/**
* @property int $id {primary}
* @property Author $author {m:1 Author::$books}
* @property Author $translator {m:1 Author::$translatedBooks}
*/
class Book extends Nextras\Orm\Entity\Entity
{}
/**
* @property int $id {primary}
* @property Author $author {m:1 Author, oneSided=true}
* @property Author $translator {m:1 Author, oneSided=true}
*/
class Book extends Nextras\Orm\Entity\Entity
{}
use Nextras\Orm\Relationships\OneHasMany;
/**
* @property int $id {primary}
* @property Category $parent {m:1 Category::$categories}
* @property OneHasMany|Category[] $categories {1:m Category::$parent}
*/
class Category extends Nextras\Orm\Entity\Entity
{}
use Nextras\Orm\Relationships\ManyHasMany;
/**
* @property int $id {primary}
* @property ManyHasMany|Tag[] $tags {m:m Tag::$books, isMain=true}
*/
class Book extends Nextras\Orm\Entity\Entity
{}
/**
* @property int $id {primary}
* @property ManyHasMany|Book[] $books {m:m Book::$tags}
*/
class Tag extends Nextras\Orm\Entity\Entity
{}
Only the non-main side is optional.
use Nextras\Orm\Relationships\ManyHasMany;
/**
* @property int $id {primary}
* @property ManyHasMany|Tag[] $tags {m:m Tag, isMain=true, oneSided=true}
*/
class Book extends Nextras\Orm\Entity\Entity
{}
use Nextras\Orm\Relationships\ManyHasMany;
/**
* @property int $id {primary}
* @property ManyHasMany|User[] $myFriends {m:m User::$friendsWithMe}
* @property ManyHasMany|User[] $friendsWithMe {m:m User::$myFriends}
*/
class User extends Nextras\Orm\Entity\Entity
{}
Reference will be stored in the book.ean_id
.
/**
* @property int $id {primary}
* @property Ean $ean {1:1 Ean::$book, isMain=true}
*/
class Book extends Nextras\Orm\Entity\Entity
{}
/**
* @property int $id {primary}
* @property Book $book {1:1 Book::$ean}
*/
class Ean extends Nextras\Orm\Entity\Entity
{}
Only the not-main side is optional. Reference will be stored in the
book.ean_id
.
/**
* @property int $id {primary}
* @property Ean $ean {1:1 Ean, isMain=true, oneSided=true}
*/
class Book extends Nextras\Orm\Entity\Entity
{}
Reference will be stored in book.next_volume_id
.
/**
* @property int $id {primary}
* @property Book|null $nextVolume {1:1 Book::$previousVolume, isMain=true}
* @property Book|null $previousVolume {1:1 Book::$nextVolume}
*/
class Book extends Nextras\Orm\Entity\Entity
{}
The example above introduces classes which weren't mentioned before:
OneHasMany
and ManyHasMany
. Instances of these classes
are injected into the property and provide some cool features. The main
responsibility is the implementation of \Traversable
interface. You
can easily iterate over the property to get the entities in the
relationship.
foreach ($author->books as $book) {
$book instanceof Book; // true
}
Also, you can use convenient methods to add, remove, and set entities in the relationship. The relationship automatically update the reverse side of the relationship (if loaded).
$author->books->add($book);
$author->books->remove($book);
$author->books->set([$book]);
$book->tags->add($tag);
$book->tags->remove($tag);
$book->tags->set([$tag]);
The relationship property wrapper accepts both entity instances and an id (primary key value). If you pass an id, Orm will load the proper entity automatically. This behavior is available only if the entity is “attached” to the repository (fetched from storage, directly attached or indirectly attached by another attached entity).
$book->author = 1;
$book->author->id === 1; // true
$book->tags->remove(1);
Sometimes, it is useful to work with the relationship as with collection to
make further adjustments. Simply call toCollection()
to receive
collection over the relationship.
$collection = $author->books->toCollection();
$collection = $collection->limitBy(3);
Working with such collection will preserve optimized loading for other entities in the original collection.
$authors = $orm->authors->findById([1, 2]); // fetches 2 authors
foreach ($authors as $author) {
// 1st call for author #1 fetches data for both authors by
// (SELECT ... WHERE author_id = 1 LIMIT 2) UNION ALL (SELECT ... WHERE author_id = 2 LIMIT 2)
// and returns data just for the author #1.
//
// 2nd call for author #2 uses already fetched data.
$sub = $author->books->toCollection()->limitBy(2);
}
You may decide to expose only the relationship's collection in its property.
Use exposeCollection
modifier argument. Further modifications are
still allowed through relationship object returned by
IEntity::getProperty()
method.
/**
* @property int|null $id
* @property Collection|Book[] $books {1:m Author::$books, exposeCollection=true}
*/
class Author
{
public function setBooks(Book ...$books): void
{
$this->getProperty('books')->set($books);
}
}
$author = new Author();
$author->books->findBy(...);
$author->setBooks(new Book());