go-database

Prevent connection pool leaks in Go by explicitly setting maximum open connections, connection idle time, and lifetime limits. Proactively ping connections to clear stale states and ensure proper resource closure to avoid overload.

Handle Go database transactions reliably by using wrapper patterns that guarantee rollback on errors. Configure appropriate isolation levels for critical operations to maintain atomicity and prevent partial data corruption.

Avoid N+1 queries and write safe SQL in Go by using parameterized queries, understanding QueryRow versus Query semantics, and properly closing rows. Adopt type-safe tooling like sqlc to enforce query safety at compile time.

Yes, this Skill supports Go projects using GORM and ent. It provides idiomatic access patterns, enforces context propagation, and guides repository interface design for testability across these different ORM and query generation tools.

Database migration best practices for a Go Postgres service involve applying reliable schema migration tooling, handling nullable columns correctly, and enforcing context propagation to prevent brittle migrations that cause outages.

Use sqlc instead of standard database/sql when you need type-safe SQL generation and compile-time query validation. Standard database/sql remains suitable for lower-level control, while sqlc reduces boilerplate and prevents runtime query errors.