Port of the table-standard change to the release/0.1 line (the same change as the pull request against develop; the two lines do not differ in this change).
Every table the QBit declares has createDate and modifyDate, date-time, not editable, set by QQQ. Nine tables gain columns: modify_date on assistant_turn_event, assistant_tool_call, assistant_feedback, assistant_usage, assistant_data_audit, assistant_budget_event, assistant_client_error and assistant_pending_action_claim, and both dates on assistant_budget_usage. Every write the QBit makes goes through QQQ's own insert and update actions, so an insert sets both and an update moves modifyDate; a table that is only inserted has modifyDate equal to createDate.
The QBit ships a reference DDL (docs/schema-postgres.sql); an additive block is appended: nullable columns defaulting to CURRENT_TIMESTAMP (no table rewrite on PostgreSQL 11 and later, safe while the previous release still runs) and an UPDATE per table giving existing rows their own creation time. See UPGRADE.md.
Tests: TableStandardDatesTest (declared tables iterated, store write paths) and TableStandardSchemaTest (the reference DDL creates the columns).
Port of the table-standard change to the `release/0.1` line (the same change as the pull request against `develop`; the two lines do not differ in this change).
Every table the QBit declares has `createDate` and `modifyDate`, date-time, not editable, set by QQQ. Nine tables gain columns: `modify_date` on `assistant_turn_event`, `assistant_tool_call`, `assistant_feedback`, `assistant_usage`, `assistant_data_audit`, `assistant_budget_event`, `assistant_client_error` and `assistant_pending_action_claim`, and both dates on `assistant_budget_usage`. Every write the QBit makes goes through QQQ's own insert and update actions, so an insert sets both and an update moves `modifyDate`; a table that is only inserted has `modifyDate` equal to `createDate`.
The QBit ships a reference DDL (`docs/schema-postgres.sql`); an additive block is appended: nullable columns defaulting to `CURRENT_TIMESTAMP` (no table rewrite on PostgreSQL 11 and later, safe while the previous release still runs) and an `UPDATE` per table giving existing rows their own creation time. See UPGRADE.md.
Tests: `TableStandardDatesTest` (declared tables iterated, store write paths) and `TableStandardSchemaTest` (the reference DDL creates the columns).
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Nine tables lacked a standard date: eight had createDate but no modifyDate
(turn events, tool calls, feedback, model calls, data audit, budget events,
client errors, pending action claims) and the budget accounting table had
neither. All nine now declare both, date-time, not editable, set by QQQ.
Every write the QBit makes goes through QQQ's own insert and update actions,
so an insert sets both and an update (an incremented daily usage counter, a
decided pending action, a cleared tool result, a scheduled run that ends, the
accounting row that follows a usage row) moves modifyDate. A table that is
only inserted has modifyDate equal to createDate.
The reference DDL gets an additive block (nullable columns defaulting to the
time of the write, so the previous release keeps working; existing rows get
the table's own creation time). Tests iterate the declared tables, exercise
the store's insert and update paths, and check the DDL creates the columns.
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
QQQ's createDate and modifyDate behaviors each read the clock, so the two
values of one insert differ by a few microseconds on a clock finer than the
machine this was first run on. The decision claim and the budget event are
written once and never change; an insert customizer on those two tables makes
modifyDate the same instant as createDate. The test of the other tables no
longer asserts equality they cannot give (they are rewritten when a
transcript is redacted).
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 table-standard change to the
release/0.1line (the same change as the pull request againstdevelop; the two lines do not differ in this change).Every table the QBit declares has
createDateandmodifyDate, date-time, not editable, set by QQQ. Nine tables gain columns:modify_dateonassistant_turn_event,assistant_tool_call,assistant_feedback,assistant_usage,assistant_data_audit,assistant_budget_event,assistant_client_errorandassistant_pending_action_claim, and both dates onassistant_budget_usage. Every write the QBit makes goes through QQQ's own insert and update actions, so an insert sets both and an update movesmodifyDate; a table that is only inserted hasmodifyDateequal tocreateDate.The QBit ships a reference DDL (
docs/schema-postgres.sql); an additive block is appended: nullable columns defaulting toCURRENT_TIMESTAMP(no table rewrite on PostgreSQL 11 and later, safe while the previous release still runs) and anUPDATEper table giving existing rows their own creation time. See UPGRADE.md.Tests:
TableStandardDatesTest(declared tables iterated, store write paths) andTableStandardSchemaTest(the reference DDL creates the columns).🤖 Generated with Claude Code