Sam's requirement, identified early September 2026 with a written report: https://static.catlow.cloud/archie-sqlc-migration-report.html (likely outdated — re-verify against the current tree before acting). Today the store layer is hand-written database/sql across internal/store (~15 files), cronstore, identities, gateway sessions, etc., with a hand-rolled migration ladder (internal/store/store.go migrateTasks, PRAGMA user_version, currently v3; v4 added 2026-09-21 for per-kind resource_history request-ID uniqueness). Adoption plan: (1) re-run/refresh the report against the current schema inventory; (2) decide sqlc config layout (one package per store surface? queries/ dir per domain); (3) goose for migrations — note sqlc does NOT manage schema migrations, so the migrate ladder is replaced by goose-managed SQL migrations while sqlc generates the query layer against the migrated schema; (4) migrate package-by-package, starting with the most churned surface; (5) keep the migration version continuity so existing archie.db files upgrade in place. Constraints: zero-downtime upgrade path for serving stores (archie-state-store owns archie.db), the store's DDL is also read by OpenReadOnly/ValidateFile (schema-version ceiling), and generated code is LAW per repo hygiene. Do not start until Sam scopes it; this bead is the durable pointer to the report and the decision.
Close reason
Obsolete: this issue targets the retired SQLite store layer; current persistence is PostgreSQL and its migration/query tooling is tracked by 1rwj.
Imported from beads archie-core-b6b4 · GitHub #1130 · type task · priority P2 · created 2026-09-21 · closed 2026-10-12
Sam's requirement, identified early September 2026 with a written report: https://static.catlow.cloud/archie-sqlc-migration-report.html (likely outdated — re-verify against the current tree before acting). Today the store layer is hand-written database/sql across internal/store (~15 files), cronstore, identities, gateway sessions, etc., with a hand-rolled migration ladder (internal/store/store.go migrateTasks, PRAGMA user_version, currently v3; v4 added 2026-09-21 for per-kind resource_history request-ID uniqueness). Adoption plan: (1) re-run/refresh the report against the current schema inventory; (2) decide sqlc config layout (one package per store surface? queries/ dir per domain); (3) goose for migrations — note sqlc does NOT manage schema migrations, so the migrate ladder is replaced by goose-managed SQL migrations while sqlc generates the query layer against the migrated schema; (4) migrate package-by-package, starting with the most churned surface; (5) keep the migration version continuity so existing archie.db files upgrade in place. Constraints: zero-downtime upgrade path for serving stores (archie-state-store owns archie.db), the store's DDL is also read by OpenReadOnly/ValidateFile (schema-version ceiling), and generated code is LAW per repo hygiene. Do not start until Sam scopes it; this bead is the durable pointer to the report and the decision.
### Close reason
Obsolete: this issue targets the retired SQLite store layer; current persistence is PostgreSQL and its migration/query tooling is tracked by 1rwj.
---
_Imported from beads `archie-core-b6b4` · GitHub #1130 · type task · priority P2 · created 2026-09-21 · closed 2026-10-12_
sam
added the mediumtask labels 2026-10-27 13:39:33 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Sam's requirement, identified early September 2026 with a written report: https://static.catlow.cloud/archie-sqlc-migration-report.html (likely outdated — re-verify against the current tree before acting). Today the store layer is hand-written database/sql across internal/store (~15 files), cronstore, identities, gateway sessions, etc., with a hand-rolled migration ladder (internal/store/store.go migrateTasks, PRAGMA user_version, currently v3; v4 added 2026-09-21 for per-kind resource_history request-ID uniqueness). Adoption plan: (1) re-run/refresh the report against the current schema inventory; (2) decide sqlc config layout (one package per store surface? queries/ dir per domain); (3) goose for migrations — note sqlc does NOT manage schema migrations, so the migrate ladder is replaced by goose-managed SQL migrations while sqlc generates the query layer against the migrated schema; (4) migrate package-by-package, starting with the most churned surface; (5) keep the migration version continuity so existing archie.db files upgrade in place. Constraints: zero-downtime upgrade path for serving stores (archie-state-store owns archie.db), the store's DDL is also read by OpenReadOnly/ValidateFile (schema-version ceiling), and generated code is LAW per repo hygiene. Do not start until Sam scopes it; this bead is the durable pointer to the report and the decision.
Close reason
Obsolete: this issue targets the retired SQLite store layer; current persistence is PostgreSQL and its migration/query tooling is tracked by 1rwj.
Imported from beads
archie-core-b6b4· GitHub #1130 · type task · priority P2 · created 2026-09-21 · closed 2026-10-12