Repository

MMO\core\entities · 1 symbol · generated 5 Oct 2026

class

Repository

Collections container.

class MMO\core\entities\Repository extends MMO\core\classes\aRepository

Namespace: MMO\core\entities
Extends: aRepository

A collection registers itself for commit when it is built ([`Collection::__construct`](https://mcp.mmoframework.fr/documentation/mmo.core/php/entities/Collection.md#collection--construct)), so a change is saved by `commit()` with nothing to register by hand. [`Collection::registerCommit`](https://mcp.mmoframework.fr/documentation/mmo.core/php/entities/Collection.md#collection-registercommit) turns that off. A minimal, purely in-memory repository: entities live only in their [`Collection`](https://mcp.mmoframework.fr/documentation/mmo.core/php/entities/Collection.md#collection) (no external backing store), so [`executeQuery`](https://mcp.mmoframework.fr/documentation/mmo.core/php/entities/Repository.md#repository-executequery) just delegates to the collection's own local filtering, ids are locally generated ([`generateId`](https://mcp.mmoframework.fr/documentation/mmo.core/php/entities/Repository.md#repository-generateid)), and [`onCommit`](https://mcp.mmoframework.fr/documentation/mmo.core/php/entities/Repository.md#repository-oncommit) has nothing to actually persist.

$repo = new Repository(); $repo->addCollection('users', new Collection(User::class, $repo, 'users'));

Index

	createEntity($class, $data, $collection)	Same as `aRepository::createEntity`, auto-assigning the next id (`generateId`) if $data has none.
	dropCollection($collection)	NOTE: this used to just `return $this->hasCollection($collection);` -- reporting whether the collection exists, but never actually removing it from `aRepository::$collections`.
	executeQuery($query, $opts)	Find entities by content (delegates to the collection's own in-memory filtering -- see `Collection::executeQuery`).
	generateId($collection)
	onCommit($commit)	There's nothing to actually persist here (entities already live in-memory in their collection) -- just logs a notice for each changed entity this repository is responsible for.
	uid()

Methods6

createEntity($class, $data, $collection)

Repository.php:70

Same as aRepository::createEntity, auto-assigning the next id (generateId) if $data has none.

function createEntity( string $class, array $data = [], ?MMO\core\interfaces\iCollection $collection = null ): MMO\core\interfaces\iEntity

$class	string
$data = []	array
$collection = null	null \| iCollection
returns	iEntity

dropCollection($collection)

Repository.php:34

NOTE: this used to just return $this->hasCollection($collection); -- reporting whether the collection exists, but never actually removing it from aRepository::$collections. Verified concretely:

function dropCollection(MMO\core\interfaces\iCollection|string $collection): bool

See: Collection::drop() (which calls this to do the actual removal) reported success, yet the collection remained fully registered and reachable via aRepository::getCollection afterward. Fixed to actually remove it (aRepository has no existing removal method to delegate to).

$collection	iCollection \| string
returns	bool	false if $collection wasn't registered.

executeQuery($query, $opts)

Repository.php:47

Find entities by content (delegates to the collection's own in-memory filtering -- see Collection::executeQuery).

function executeQuery(MMO\core\entities\Query $query, array $opts = []): Generator

$query	Query
$opts = []	array
returns	Generator

generateId($collection)

Repository.php:55

function generateId(MMO\core\interfaces\iCollection $collection): int

$collection	iCollection
returns	int	one more than the highest existing (loaded) entity id, numerically -- or 1 if the collection is empty.

onCommit($commit)

Repository.php:80

There's nothing to actually persist here (entities already live in-memory in their collection) -- just logs a notice for each changed entity this repository is responsible for.

function onCommit(MMO\core\events\Commit $commit): void

$commit	Commit
returns	void

uid()

Repository.php:21

function uid(): string

returns

string

Inherited members (28)

	Properties	Declared by	Description
	`collections`	aRepository

Methods	Declared by	Description
`addCollection($name, $collection)`	aRepository	Add collection
`createCollection($name, $entityClass, $collectionId)`	aRepository	Create and register a plain `Collection` for entities of $entityClass.
`createLog($type, $origin, $collection, $data, $filters, $sorts, $limit, $offset)`	aRepository	Build (but not dispatch) a `LogQuery` entity describing a data-mutating operation, stored in the repository's LogQuery collection (if one is registered).
`debugName()`	aRepository
`forceCommit($origin, $entities)`	aRepository
`getCollection($name)`	aRepository
`getCollectionByClass($entityClass, $allowChildClass)`	aRepository	Find the collection whose entities are (an exact match, or optionally a subclass of) $entityClass.
`getCollectionName($collection)`	aRepository
`getCollections()`	aRepository
`getDistinct($collection, $key)`	aRepository	Every value one property takes across a collection, once each, in ascending order.
`getEntities()`	aRepository
`getIterator()`	aRepository	\IteratorAggregate::getIterator -- iterates name => iCollection
`hasCollection($collection)`	aRepository
`hideLogData($collection, $data)`	aRepository	What a repository logs is what it wrote (mmo.pdo's row, mmo.mongodb's document or its changes), hidden properties (`ArrayProperty::isHidden`) included, and a log is exported…
`logDelete($origin, $collection, $data, $filters, $sorts, $limit, $offset)`	aRepository	Log and dispatch a DELETE operation.
`logInsert($origin, $collection, $data, $filters, $sorts, $limit, $offset)`	aRepository	Log and dispatch an INSERT operation.
`logStatus($origin, $collection, $data, $filters, $sorts, $limit, $offset)`	aRepository	Log and dispatch a STATUS-change operation.
`logUpdate($origin, $collection, $data, $filters, $sorts, $limit, $offset)`	aRepository	Log and dispatch an UPDATE operation.
`offsetExists($key)`	aRepository	\ArrayAccess::offsetExists
`offsetGet($key)`	aRepository	\ArrayAccess::offsetGet
`offsetSet($key, $value)`	aRepository	\ArrayAccess::offsetSet -- equivalent to `addCollection`
`offsetUnset($key)`	aRepository	\ArrayAccess::offsetUnset
`onFetch($event)`	aRepository	Listener for `Fetch`: resolves a `repository-uid/collection-id#id` (or `repository-uid/collection-id#id/nested/path` for an embedded value) URL, what `Ent…`
`searchText($query, $text)`	aRepository	Full-text search. Not implemented at this level -- a concrete repository backed by a search-capable store should override this.
`setCollections($cols)`	aRepository	Register a batch of collections at once, e.g.
`__construct($collections)`	aRepository
`__wakeup()`	aRepository	Register this repository's `onCommit` / `onFetch` as listeners on the global