samber/cc-skills-golang / skills/golang-database
golang-database
VerifiedComprehensive guide for Go database access — parameterized queries, struct scanning, NULLable columns, transactions, isolation levels, SELECT FOR UPDATE, connection pool, batch processing, context propagation, and migration tooling. Use when writing, reviewing, or debugging Golang code that interacts with PostgreSQL, MariaDB, MySQL, or SQLite; for database testing; or for questions about database/sql, sqlx, or pgx. Does NOT generate database schemas or migration SQL.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 11.3 KB |
| evals/evals.json | config | 15.0 KB |
| references/performance.md | markdown | 9.0 KB |
| references/scanning.md | markdown | 2.2 KB |
| references/testing.md | markdown | 6.5 KB |
| references/transactions.md | markdown | 1.5 KB |
references/scanning.md
View on GitHub# Struct Scanning and NULLable Columns
## Struct Scanning with sqlx
Tag struct fields with `db:"column_name"` for sqlx:
```go
type User struct {
ID int64 `db:"id"`
Name string `db:"name"`
Email string `db:"email"`
DeletedAt *time.Time `db:"deleted_at"` // NULLable
}
// Single row
var user User
err := db.GetContext(ctx, &user, "SELECT id, name, email, deleted_at FROM users WHERE id = $1", id)
// Multiple rows
var users []User
err := db.SelectContext(ctx, &users, "SELECT id, name, email, deleted_at FROM users WHERE active = true")
```
## Struct Scanning with pgx
With pgx (v5+), use `pgx.CollectRows` for automatic struct mapping:
```go
rows, err := pool.Query(ctx, "SELECT id, name, email FROM users WHERE active = true")
if err != nil {
return fmt.Errorf("querying users: %w", err)
}
users, err := pgx.CollectRows(rows, pgx.RowToStructByName[User])
```
## JSON Marshaling
Struct tags for both database and JSON work together. Pointer fields marshal to `null` in JSON when NULL in the database:
```go
type User struct {
ID int64 `db:"id" json:"id"`
Name string `db:"name" json:"name"`
Email string `db:"email" json:"email"`
Bio *string `db:"bio" json:"bio,omitempty"` // NULL → omitted in JSON
DeletedAt *time.Time `db:"deleted_at" json:"deleted_at"` // NULL → null in JSON
}
```
## NULLable Columns
Three approaches, from most to least recommended:
**1. Pointer fields (recommended)** — clean, works with JSON marshaling:
```go
type User struct {
ID int64 `db:"id" json:"id"`
Name string `db:"name" json:"name"`
DeletedAt *time.Time `db:"deleted_at" json:"deleted_at"` // nil when NULL
}
// Check: if user.DeletedAt != nil { ... }
```
**2. `sql.NullXxx` types** or `sql.Null[T]` generic — explicit but verbose, requires custom JSON marshaling:
```go
type User struct {
ID int64 `db:"id"`
Bio sql.NullString `db:"bio"`
}
// Check: if user.Bio.Valid { use(user.Bio.String) }
```
**3. `COALESCE` in SQL** — moves NULL handling to the query:
```sql
SELECT id, COALESCE(bio, '') AS bio FROM users WHERE id = $1
```
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |