Doctrine-inspired ORM primitives that keep WordPress wpdb as the database
runtime. Read docs/api-and-architecture.md before changing persistence,
mapping, query compilation, or schema behavior.
src/Metadata/: attributes and metadata validation.src/Query/: DQL subset, query builder, placeholders, and hydration metadata.src/Dbal/: thewpdbadapter and SQL platform.src/UnitOfWork.phpandsrc/EntityManager.php: write lifecycle and identity map.tests/Integration/OrmWorkflowTest.php: broad persistence contract.
- Focused:
vendor/bin/phpunit --configuration phpunit.xml.dist --filter <TestName> - Full:
composer qa
Add a focused regression test for parser, metadata, cache, or database failure paths before changing them. Keep PHPUnit warnings and risky tests fatal.
flush()is the only point that sends scheduled writes to the database.- Query values must remain
wpdbparameters; only validated identifiers may be interpolated into SQL. - Unsupported DQL and missing parameters must fail explicitly, never broaden a query silently.
- Preserve transaction nesting and surface an unavailable
wpdbruntime. - Schema changes must not become destructive without an explicit caller choice.
sympress/kerneldiscoversOrmBundlethroughcomposer.json.sympress/migrationconsumes the bridge insrc/Bridge/Migration/.- Public mapping, query, and entity-manager changes require a consumer search before release.
The smallest relevant test passes, composer qa passes, documentation matches
the supported DQL subset, and no generated/vendor files are committed.