repository

To enforce consistent CRUD vocabulary for PostgreSQL repositories, apply a fixed method set including create, select, update, delete, and upsert. This standardizes data access operations across models, ensuring predictable method names and integrity constraint handling.

Standardizing Result[T] returns and error handling in domain-driven SQL repositories requires wrapping CRUDRepository methods and using on_integrity decorators. This pattern ensures consistent error capture for unique constraints across all create, update, and upsert flows.

Implement pagination and ordering in PostgreSQL repositories by applying helper functions like sqla_select and sqla_offset_query. These standardized helpers enforce predictable data loading and pagination structures across your data access layer.

Yes, the repository pattern supports automatic handling of unique constraint violations by enforcing the use of on_integrity decorators. This mechanism safely captures and manages database integrity errors during create and upsert operations.

Validate repository anatomy by checking that your class inherits BaseRepository, interacts safely with DBGateway, and uses self._crud for operations. This structural enforcement guarantees repositories follow the required PostgreSQL data access pattern.