Download the PHP package sirix/cycle-orm-factory without Composer

Mezzio Cycle ORM Factory

Migration guides:

• v1 to v2
• v2 to v3
• v3 to v4

Factories for integrating Cycle ORM into Mezzio with a runtime-focused schema pipeline.

Installation

Optional packages:

• symfony/console: required for built-in CLI commands.
• laminas/laminas-cli: optional CLI integration for Mezzio/Laminas.
• cycle/migrations: required for migration runtime commands.
• cycle/schema-migrations-generator: required for cycle:schema:migration:generate.
• cycle/entity-behavior and cycle/entity-behavior-uuid: optional behavior events; runtime falls back to default Cycle command generator if not installed.

Configuration

Create config/autoload/cycle-orm.global.php:

Runtime schema contract (v3)

Runtime behavior is controlled by cycle.schema.cache.enabled.

When true:

• ORM tries to load compiled schema from cycle.schema.compiled.path.
• If file exists: schema is loaded via require and ORM is created.
• If file is missing: schema is compiled on first start, persisted to file, then reused.

When false:

• Schema is compiled on every start in memory.
• No compiled schema file is read or written by runtime.

Recommended production setup:

• keep cache.enabled=true
• run cycle:schema:compile during build/release.

Additional schema generators

cycle.generators supports:

• service ID from container,
• generator FQCN with zero-arg constructor,
• direct instance implementing Cycle\Schema\GeneratorInterface.

Invalid entries throw Cycle\ORM\Exception\ConfigException.

Collection factories

cycle.collections configures Cycle ORM collection factories for *Many relations. It works with the built-in Cycle factories and with custom implementations of Cycle\ORM\Collection\CollectionFactoryInterface.

Factory definitions support:

• service ID from container,
• factory FQCN with zero-arg constructor,
• direct instance implementing Cycle\ORM\Collection\CollectionFactoryInterface.

Custom collection factories may use the same short form as built-in factories:

With the short form, the package registers the factory by alias and lets Cycle infer the collection interface from CustomCollectionFactory::getInterface(). If the factory class has constructor dependencies, register it as a container service and use that service ID instead of the class name.

Use the extended definition only when you need to explicitly provide a base collection class or interface for collection: CustomCollection::class matching:

The factory value in the extended definition accepts the same inputs as the short form: a container service ID, a factory FQCN with a zero-arg constructor, or a direct factory instance.

For ManyToMany pivot entity access specifically, use a collection factory that supports Cycle pivoted collections. Cycle's Doctrine collection factory provides that support, so install doctrine/collections, register doctrine, and set the relation collection to doctrine.

Manual mapping key compatibility

Manual schema definitions are configured with cycle.schema.manual_mapping_schema_definitions.

Services

Aliases provided by ConfigProvider:

• orm -> Cycle\ORM\ORMInterface
• dbal -> Cycle\Database\DatabaseInterface

Migration aliases provided only when cycle/migrations is installed:

• migrator -> Sirix\Cycle\Service\MigratorInterface

Repository services

RepositoryFactory exposes a custom Cycle repository as a container service without injecting ORMInterface into application code. Assign the repository class to an entity in the Cycle schema, register it with the factory, and alias your application interface to it:

The factory resolves the repository class from the compiled Cycle schema and asks Cycle for the corresponding entity role. It supports custom read repositories and repositories that add persist methods through EntityManager.

See the Repository Services guide for read and persist repository examples, manual schema configuration, string roles, aliases, and schema-cache refresh requirements.

CLI commands

Commands are registered only when symfony/console is installed.

cycle:schema:* commands:

• cycle:schema:compile: compile schema and store compiled file.
• cycle:schema:sync: run sync pipeline; refresh compiled file only when cache is enabled.
• cycle:schema:migration:generate: generate migrations via schema pipeline; available only with cycle/migrations and cycle/schema-migrations-generator.

Other commands:

• cycle:cache:clear: remove compiled schema file.
• cycle:migration:run
• cycle:migration:rollback
• cycle:migration:create
• cycle:seed:create
• cycle:seed:run

Migration/seed command availability:

• registered only when cycle/migrations is installed.

Create migration notes

cycle:migration:create supports --database (-b). Generated filename includes database alias:

• <timestamp>_0_<counter>_<database-alias>_<migration_name_in_snake_case>.php

CLI usage examples

With laminas-cli:

With standalone Symfony Console (manual command wiring in your app):

Performance note

Compiled schema is stored as plain PHP and loaded by require, which works well with OPcache and avoids PSR-6 serialization overhead in runtime hot paths.

More

• Cycle ORM documentation