orm-patterns

To fix N+1 query problems in PHP ORM projects, apply eager loading instead of lazy loading for related records. This skill helps spot N+1 issues during code review and guides selecting the correct loading strategy to optimize data access performance.

Use Active Record for simpler domain logic and Data Mapper for complex business rules requiring loose coupling and high testability. This skill provides evaluation guidelines to distinguish these ORM patterns, their anti-patterns, and when to apply each for scalable data access.

Defining safe cascade rules for ORM relationships requires evaluating your entity dependencies and lifecycle operations. This skill provides guidelines for relationship cascading, query builder composition, and scopes to ensure robust data access without orphaned records or unintended deletions.

Yes, you can implement optimistic locking and soft deletes within PHP ORM patterns. This skill covers these specific features alongside identity maps and unit of work patterns to help you design robust data access layers that prevent concurrent update conflicts and preserve data history.

Common ORM anti-patterns hurting PHP performance include unoptimized lazy loading causing N+1 queries, improper relationship cascading, and misconfigured identity maps. This skill helps identify these issues through performance profiling guidelines to achieve maintainable, performant data access.

Yes, this skill provides specific guidelines for reviewing and optimizing ORM-layer code within the php-api-builder library. It supports evaluating Active Record and Data Mapper implementations to achieve scalable, performant data access tailored to that environment.