Design a clean Go data access layer with the standard database/sql, query patterns, transactions, and connection tuning.
## CONTEXT I am building the database layer of a Go service and want it clean, testable, and performant. I need guidance on database/sql or a thin query layer, transaction handling, connection pool tuning, and a repository pattern that does not leak SQL into business logic. Assume PostgreSQL or a similar SQL database…
Premium Prompt
Unlock this prompt — and all 25,000+ expert-crafted prompts — with Pro.
Unlock with Pro