Story: sqlgen follow-up
Table of Contents
This page documents a story in Sprint 12. It captures the goal, current status, acceptance criteria, and the tasks that compose it.
Goal
Continue the sqlgen work started in sprint 11. Bound-parameters adoption and raw-libpq removal both require a vcpkg release of the merged upstream features.
Status
| Field | Value |
|---|---|
| State | BLOCKED |
| Parent sprint | Sprint 12 |
| Now | BLOCKED on upstream + vcpkg release. |
| Waiting on | vcpkg picking up the sqlgen release. |
| Next | Resume once vcpkg has the release. |
| Last touched | 2026-02-20 |
Continued from: sqlgen improvements (sprint 11). The upstream work landed in sqlgen main, but vcpkg hasn't picked up a release yet, so both bound-parameters adoption and the raw-libpq removal remain blocked.
Acceptance
- Native sqlgen bound parameters adopted; libpq escapes retired.
- Raw libpq absent from ores.* code.
Tasks
| Task | State | Start | End | Description |
|---|---|---|---|---|
| Add bound parameters to sqlgen | BLOCKED | 2026-05-19 | Adopt native sqlgen bound-parameter support once vcpkg picks up the release. | |
| Remove uses of raw libpq | BLOCKED | 2026-05-19 | Replace remaining raw libpq calls with sqlgen calls once vcpkg picks up the sqlgen release with the new features. |
Decisions
- Track upstream releases through vcpkg
- avoids carrying local patches.
Out of scope
- Forking sqlgen.
See also
- sqlgen improvements (sprint 11) — predecessor.