Port of the develop change to the 0.1 release line; the two lines differ only in the pom version.
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.
Port of the develop change to the 0.1 release line; the two lines differ only in the pom version.
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)
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>
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.
Port of the develop change to the 0.1 release line; the two lines differ only in the pom version.
Every table the qbit declares now has
createDateandmodifyDate(date-time, not editable, QQQ create-date and modify-date behaviors).db_perf_snapshotgainsmodifyDate, the other six get the behaviors and not-editable on the fields they had.captured_at/requested_atwhere the table has one, otherwise the migration time; empty dates in the tables that already had the columns are filled.DbPerfStore, the attribution flusher); there is no hand-written SQL write, so QQQ maintains the dates.Gated
./mvnw verify: 128 tests, 0 failures, Checkstyle 0 violations, coverage gate met.🤖 Generated with Claude Code