symfonydoctrine-transactions
Handle database transactions with Doctrine UnitOfWork; implement optimistic locking, flush strategies, and transaction boundaries
When & Why to Use This Skill
This Claude skill specializes in managing complex database transactions within the Symfony framework using Doctrine ORM. It provides expert assistance in implementing the UnitOfWork pattern, defining precise transaction boundaries, and utilizing optimistic locking to ensure data integrity and high performance in PHP applications.
Use Cases
- Case 1: Implementing ACID-compliant transactions across multiple entities to ensure data consistency during complex business operations.
- Case 2: Configuring optimistic locking strategies to prevent 'lost update' issues in high-concurrency web environments.
- Case 3: Optimizing database performance by managing Doctrine flush strategies and reducing unnecessary write operations.
- Case 4: Refactoring legacy Symfony code to establish clear transaction boundaries and improve the reliability of the persistence layer.
| name | symfony:doctrine-transactions |
|---|---|
| description | Use when symfony doctrine transactions |
symfony:doctrine-transactions (Micro)
Use when
- Use when symfony doctrine transactions
Rules
- Keep changes minimal and focused
- Ask before running servers/builds/tests
- Load reference/examples only on explicit request
References
reference.mddocs/complexity-tiers.md