Files
db-sqlite/.gitea/pull_request_template.md
Rene Nochebuena 0acf4da97e feat(db-sqlite): initial implementation — database/sql SQLite with lifecycle and UnitOfWork (v1.0.0)
Introduces code.nochebuena.dev/einherjar/db-sqlite — the SQLite database starter
for the Einherjar framework. Absorbs the sqlite package from micro-lib using the
pure-Go modernc.org/sqlite driver (no CGO, cross-compilation compatible).

Interfaces (CT-6: one TypeSpec per file):
- Executor — ExecContext, QueryContext, QueryRowContext (database/sql types)
- Tx — Executor + Commit(), Rollback() — no ctx; honest database/sql contract
- Provider — GetExecutor, Begin, Ping, HandleError
- Component — lifecycle.Component + observability.Checkable + Provider
- UnitOfWork — Do(ctx, fn)

Implementation:
- New(logger, cfg) Component — pool not created until OnInit
- OnInit: sql.Open with DSN (Path + Pragmas); sets MaxOpenConns, MaxIdleConns
- OnStart: Ping with 5s timeout; logs "sqlite: connected"
- OnStop: db.Close(); logs "sqlite: closing pool"
- GetExecutor: returns active Tx from context (ctxTxKey) or *sql.DB; explicit
  nil return when db uninitialized to avoid typed-nil interface pitfall
- Begin: wraps db.BeginTx; wrapped in xerrors on error
- HealthCheck: delegates to Ping; Priority LevelDegraded (file DB; absence
  is non-fatal on a server restart — file always present if configured)
- NewUnitOfWork(logger, provider) UnitOfWork — acquires writeMu before Begin
  to prevent SQLITE_BUSY under concurrent goroutines (SQLite single-writer model)
- writeMu: extracted from *sqliteImpl via type assertion in NewUnitOfWork;
  gracefully skipped when provider is a mock (nil mu)
- HandleError: sql.ErrNoRows→ErrNotFound, unique/pk constraint→ErrAlreadyExists,
  foreign key→ErrInvalidInput, all others→ErrInternal

Config (EINHERJAR_SQLITE_* env vars):
  Path(required), MaxOpenConns(1), MaxIdleConns(1),
  Pragmas(?_journal=WAL&_timeout=5000&_fk=true)

- Component interface embeds observability.Identifiable; identifiable.go implements
  ModulePath and ModuleVersion via runtime/debug.ReadBuildInfo() — prints in launcher banner
2026-05-29 15:56:45 +00:00

71 lines
2.3 KiB
Markdown

## Summary
<!-- One or two sentences: what does this PR do and why? -->
---
## Type of change
- [ ] Bug fix — non-breaking change that resolves an issue
- [ ] New feature — non-breaking addition of functionality
- [ ] Breaking change — alters existing behavior or public API
- [ ] Documentation update
- [ ] Refactor — no functional change, no new API surface
- [ ] Test improvement
---
## Description
<!--
Provide enough context for a reviewer who was not in the room:
- What problem does this solve?
- What approach did you choose, and why?
- Were there alternatives you considered and rejected?
- Any known limitations or follow-up work?
-->
---
## Testing
- [ ] I added or updated tests that cover my changes
- [ ] All tests pass locally — `go test ./...`
- [ ] No formatting issues — `gofmt -l .` produces no output
- [ ] No vet warnings — `go vet ./...` is clean
---
## Checklist
- [ ] At most one exported type per non-test `.go` file (CT-6)
- [ ] No new external dependencies added without prior discussion in an issue
- [ ] Public API changes are reflected in `CHANGELOG.md`
- [ ] Breaking changes include a migration note in the PR description above
---
## Contributor License Agreement
> **This PR will not be merged until the CLA comment is present.**
Before a Maintainer reviews your code, you must post the following text **as a comment on this PR** — not here in the description. PR description checkboxes can be silently toggled by anyone; a comment is a timestamped, author-attributed record that cannot be quietly removed.
**Copy and post this exact text as a PR comment:**
---
> I have read the Einherjar Contributor License Agreement (CLA.md) and I agree to all its terms.
> I confirm this Contribution is my original work. I grant the Maintainers the rights described
> therein, including the right to relicense, and I retain ownership of my copyright.
> This agreement covers all future Contributions I submit to any Einherjar repository under
> this account.
---
First time contributing? Read [CLA.md](../CLA.md) for the full agreement before posting the comment.
If you are contributing on behalf of a company, an authorized representative of that company must post the comment.
<!-- Thank you for contributing to Einherjar. For those who come after. -->