答案：Go中数据库错误处理需通过errors.As提取底层错误并结合SQL状态码进行精准转换，避免依赖错误消息字符串。应封装统一的错误映射函数，将驱动错误（如PostgreSQL的23505唯一键冲突）转化为应用级错误，提升代码健壮性与可维护性。
在Go语言开发中，错误处理和数据库操作是两个高频且关键的环节，尤其当涉及数据库SQL执行时，如何准确识别和转换底层错误，对提升系统健壮性和用户体验至关重要。Go的错误处理机制简洁但需要开发者主动判断，而数据库驱动（如
database/sql或
pgx）返回的错误往往封装较深，直接使用容易造成误判。以下是实用的错误处理策略与SQL错误转换技巧。
理解Go的错误处理机制
Go通过返回
error类型来表示异常状态，函数执行失败时通常返回非nil的error。正确的做法是始终检查error值，并根据具体类型或内容做出响应。
常见模式如下：
<span style="color:#00007f">rows</span>, <span style="color:#00007f">err</span> := <span style="color:#007f7f">db</span>.<span style="color:#7f007f">Query</span>(<span style="color:#7f007f">"SELECT name FROM users WHERE id = ?"</span>, userID)
<span style="color:#7f0000"><strong>if</strong></span> err != <span style="color:#7f0000"><strong>nil</strong></span> {
<span style="color:#7f007f">log</span>.<span style="color:#7f007f">Printf</span>(<span style="color:#7f007f">"query failed: %v"</span>, err)
<span style="color:#7f0000"><strong>return</strong></span> err
}
<span style="color:#7f0000"><strong>defer</strong></span> rows.<span style="color:#7f007f">Close</span>()
注意：不要忽略error，即使你认为“它不会出错”。
立即学习“go语言免费学习笔记（深入）”；
区分数据库错误类型：使用errors.Is和errors.As
database/sql本身不暴露具体错误类型，但底层驱动（如
mysql、
pq、
pgx）会返回特定错误。使用
errors.As可以提取底层错误进行判断。
例如，PostgreSQL使用
pgconn.PgError表示SQL状态码错误：
<span style="color:#00007f">_, err</span> := <span style="color:#007f7f">db</span>.<span style="color:#7f007f">Exec</span>(<span style="color:#7f007f">"INSERT INTO users (email) VALUES ($1)"</span>, <span style="color:#7f007f">"duplicate@example.com"</span>)
<span style="color:#7f0000"><strong>var</strong></span> pgErr *<span style="color:#7f007f">pgconn</span>.<span style="color:#7f007f">PgError</span>
<span style="color:#7f0000"><strong>if</strong></span> errors.<span style="color:#7f007f">As</span>(err, &pgErr) {
<span style="color:#7f0000"><strong>switch</strong></span> pgErr.<span style="color:#7f007f">Code</span> {
<span style="color:#7f0000"><strong>case</strong></span> <span style="color:#7f007f">"23505"</span>: <span style="color:#228b22">// unique_violation</span>
<span style="color:#7f007f">return</span> <span style="color:#7f007f">fmt</span>.<span style="color:#7f007f">Errorf</span>(<span style="color:#7f007f">"email already exists"</span>)
<span style="color:#7f0000"><strong>case</strong></span> <span style="color:#7f007f">"23503"</span>: <span style="color:#228b22">// foreign_key_violation</span>
<span style="color:#7f007f">return</span> <span style="color:#7f007f">fmt</span>.<span style="color:#7f007f">Errorf</span>(<span style="color:#7f007f">"referenced resource not found"</span>)
}
}
MySQL驱动如
go-sql-driver/mysql也提供
*mysql.MySQLError，可通过
Number字段判断错误码。
封装错误转换函数提升可维护性
将数据库错误映射为应用级错误，避免业务逻辑中直接处理驱动错误。可以定义统一转换函数：
<span style="color:#7f007f"><strong>func</strong></span> <span style="color:#00007f">mapSQLError</span>(err error) error {
<span style="color:#7f0000"><strong>if</strong></span> err == <span style="color:#7f0000"><strong>nil</strong></span> {
<span style="color:#7f0000"><strong>return</strong></span> <span style="color:#7f0000"><strong>nil</strong></span>
}
<span style="color:#7f0000"><strong>var</strong></span> pgErr *<span style="color:#7f007f">pgconn</span>.<span style="color:#7f007f">PgError</span>
<span style="color:#7f0000"><strong>if</strong></span> errors.<span style="color:#7f007f">As</span>(err, &pgErr) {
<span style="color:#7f0000"><strong>switch</strong></span> pgErr.<span style="color:#7f007f">Code</span> {
<span style="color:#7f0000"><strong>case</strong></span> <span style="color:#7f007f">"23505"</span>:
<span style="color:#7f0000"><strong>return</strong></span> <span style="color:#7f007f">ErrDuplicateEntry</span>
<span style="color:#7f0000"><strong>case</strong></span> <span style="color:#7f007f">"23503"</span>:
<span style="color:#7f0000"><strong>return</strong></span> <span style="color:#7f007f">ErrForeignKeyViolation</span>
<span style="color:#7f0000"><strong>case</strong></span> <span style="color:#7f007f">"22P02"</span>: <span style="color:#228b22">// invalid_text_representation</span>
<span style="color:#7f0000"><strong>return</strong></span> <span style="color:#7f007f">ErrInvalidInput</span>
}
}
<span style="color:#7f0000"><strong>return</strong></span> <span style="color:#7f007f">ErrDatabase</span> <span style="color:#228b22">// 通用数据库错误</span>
}
这样在handler或service中只需处理业务错误，逻辑更清晰。
利用SQL状态码而非错误消息
不要依赖错误消息字符串进行判断，因为可能随语言或版本变化。SQL标准定义了
SQLSTATE代码（五位字符串），如PostgreSQL和MySQL都支持，应优先使用
Code或
Number字段。
例如：
- 23505: 唯一键冲突（PostgreSQL）
- 1062: MySQL中的重复条目错误
- 22001: 字符串数据过长
这些代码比文本错误更稳定，适合作为程序判断依据。
基本上就这些。关键是建立统一的错误映射机制，避免在业务代码中散落数据库驱动相关的错误判断。通过
errors.As提取底层错误，结合SQL状态码做精准转换，能让系统更健壮，也便于测试和维护。
