gorm-error-handling

What problem does it solve?

GORM operations often return errors that, if not handled correctly, can cause crashes, data corruption, or silent failures, making debugging and reliability difficult.

Core Features & Use Cases

• Unified Error Types: Standardized error constants like ErrRecordNotFound, ErrDuplicatedKey, and transaction errors.
• TranslateError Support: Enables database‑agnostic error handling across MySQL, PostgreSQL, SQLite, and SQL Server.
• Practical Patterns: Service‑layer wrappers, transaction rollback handling, and row‑affected checks for CRUD operations.
• Use Case Example: In a Go microservice, use this skill to detect duplicate key violations during user creation and return a friendly “user already exists” message.

Quick Start

Invoke the skill with a request to check for errors after a GORM operation and receive a summarized handling strategy.