ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
I'm running a small, low-traffic PHP application on Doctrine ORM (2.x/3.x line) and want to cut database and CPU costs. I've already set associations to lazy fetch and pre-generated proxies with auto_generate_proxy_classes disabled in production, which removed most of the obvious overhead. The remaining decision is the metadata and query cache backend. The d
Pagination Strategy for Large Datasets When managing tables containing millions of records in Doctrine ORM, the choice of pagination strategy affects database execution time and memory usage. The built‑in Doctrine\\ORM\\Tools\\Pagination\\Paginator uses the SQL OFFSET clause, which requires the database to scan and discard all preceding rows. As page depth i
I am processing a large result set in a long-running PHP CLI job using Doctrine ORM. Memory usage climbs steadily as the loop iterates, which I understand is the UnitOfWork identity map retaining every managed entity. The documented mitigation is periodic flush() followed by EntityManager::clear() , but I am unsure how to apply it safely in my case. My loop
Goal: ensure that a rollback can safely revert a schema change performed by Doctrine DBAL's ALTER TABLE. Constraint: MySQL and MariaDB execute DDL outside transaction boundaries by default, Schema Manager's dropColumn and addColumn perform immediate DDL without wrapping, and MySQL 5.x auto‑commits each statement while 8.0+ may allow atomic DDL; Doctrine's Tr
When migrating a project to Doctrine ORM 3.0, we aim to define a composite primary key that includes fields from an embeddable class using PHP 8 attributes. The current documentation states that the #[ORM\Id] attribute must be placed on scalar fields of the owning entity and does not permit identifier mapping inside embeddable classes. We need to clarify whe
doctrine