feat: createDate and modifyDate on every table #41

Merged
james.maes merged 1 commits from feat/table-standard-dates into develop 2026-11-20 15:58:03 +00:00
Owner

Every table the qbit declares now has createDate and modifyDate (date-time, not editable, QQQ create-date and modify-date behaviors).

  • All 17 tables: 10 gain both fields, db_perf_snapshot gains modifyDate, the other six get the behaviors and not-editable on the fields they had.
  • Schema: append-only changesets 35 to 51. New columns are nullable with a default of the current time (safe while the previous release runs; no table rewrite on PostgreSQL 11 and newer). Existing rows get captured_at / requested_at where the table has one, otherwise the migration time; empty dates in the tables that already had the columns are filled.
  • Write paths: every table is written through QQQ's insert and update actions (DbPerfStore, the attribution flusher); there is no hand-written SQL write, so QQQ maintains the dates.
  • Tests: every declared table has both dates typed and maintained; the changelog creates the columns (and a row from a release that does not know them still gets both); an insert and update through the store set and move the dates; an upgrade from the previous changelog fills existing rows. They fail without the change.
  • Host notes: UPGRADE.md carries the PostgreSQL statements for hosts with hand-written migrations.

Gated ./mvnw verify: 128 tests, 0 failures, Checkstyle 0 violations, coverage gate met.

🤖 Generated with Claude Code

Every table the qbit declares now has `createDate` and `modifyDate` (date-time, not editable, QQQ create-date and modify-date behaviors). - All 17 tables: 10 gain both fields, `db_perf_snapshot` gains `modifyDate`, the other six get the behaviors and not-editable on the fields they had. - Schema: append-only changesets 35 to 51. New columns are nullable with a default of the current time (safe while the previous release runs; no table rewrite on PostgreSQL 11 and newer). Existing rows get `captured_at` / `requested_at` where the table has one, otherwise the migration time; empty dates in the tables that already had the columns are filled. - Write paths: every table is written through QQQ's insert and update actions (`DbPerfStore`, the attribution flusher); there is no hand-written SQL write, so QQQ maintains the dates. - Tests: every declared table has both dates typed and maintained; the changelog creates the columns (and a row from a release that does not know them still gets both); an insert and update through the store set and move the dates; an upgrade from the previous changelog fills existing rows. They fail without the change. - Host notes: UPGRADE.md carries the PostgreSQL statements for hosts with hand-written migrations. Gated `./mvnw verify`: 128 tests, 0 failures, Checkstyle 0 violations, coverage gate met. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
james.maes added 1 commit 2026-11-20 14:44:32 +00:00
feat: createDate and modifyDate on every table
maven / build (push) Successful in 4m55s
build / maven (push) Successful in 4m54s
19a0b82e7a
All 17 tables declare both dates (date-time, not editable, QQQ create-date and
modify-date behaviors). Changesets 35 to 51 add the missing columns, nullable
with a default of the current time so a previous release keeps working during
a rolling deployment, and fill existing rows. Upgrade notes carry the host DDL.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
james.maes merged commit 30d9a7c536 into develop 2026-11-20 15:58:03 +00:00
Sign in to join this conversation.