Brings every table to the QQQ table standard: createDate and modifyDate, DATE_TIME, not editable, with the CREATE_DATE and MODIFY_DATE behaviors.
sql_workbench_notebook_version, sql_workbench_result_snapshot and sql_workbench_execution gain modifyDate (column modify_date, nullable). The other three tables already had both columns; they now carry the behaviors.
Every write the qbit makes to its own tables goes through QQQ's insert and update actions (no JDBC writer), so the behaviors cover them. On the append-only tables (versions, audit) modifyDate equals createDate on insert.
docs/ddl/postgres.sql creates the column and adds an idempotent upgrade block (nullable column, catalog-only change, backfill with row locks only); UPGRADE.md has the host steps to run before deploying.
Tests: every declared table has both dates with both behaviors; version, audit and snapshot rows carry them; the shipped DDL has the columns.
No change to the read-only account the SQL runs under or to what it may read.
Gated build: CI=true ./mvnw verify, 151 unit and 10 Postgres integration tests, JaCoCo gate met.
Port of the develop change; the two lines differ only in the version in the pom.
Brings every table to the QQQ table standard: `createDate` and `modifyDate`, `DATE_TIME`, not editable, with the `CREATE_DATE` and `MODIFY_DATE` behaviors.
- `sql_workbench_notebook_version`, `sql_workbench_result_snapshot` and `sql_workbench_execution` gain `modifyDate` (column `modify_date`, nullable). The other three tables already had both columns; they now carry the behaviors.
- Every write the qbit makes to its own tables goes through QQQ's insert and update actions (no JDBC writer), so the behaviors cover them. On the append-only tables (versions, audit) `modifyDate` equals `createDate` on insert.
- `docs/ddl/postgres.sql` creates the column and adds an idempotent upgrade block (nullable column, catalog-only change, backfill with row locks only); UPGRADE.md has the host steps to run before deploying.
- Tests: every declared table has both dates with both behaviors; version, audit and snapshot rows carry them; the shipped DDL has the columns.
- No change to the read-only account the SQL runs under or to what it may read.
Gated build: `CI=true ./mvnw verify`, 151 unit and 10 Postgres integration tests, JaCoCo gate met.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Port of the develop change; the two lines differ only in the version in the pom.
Every table has createDate and modifyDate (DATE_TIME, not editable, QQQ
CREATE_DATE / MODIFY_DATE behaviors). Adds modifyDate to the notebook version,
result snapshot and execution tables, with an append-only upgrade block in
docs/ddl/postgres.sql, upgrade notes and tests.
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.
Brings every table to the QQQ table standard:
createDateandmodifyDate,DATE_TIME, not editable, with theCREATE_DATEandMODIFY_DATEbehaviors.sql_workbench_notebook_version,sql_workbench_result_snapshotandsql_workbench_executiongainmodifyDate(columnmodify_date, nullable). The other three tables already had both columns; they now carry the behaviors.modifyDateequalscreateDateon insert.docs/ddl/postgres.sqlcreates the column and adds an idempotent upgrade block (nullable column, catalog-only change, backfill with row locks only); UPGRADE.md has the host steps to run before deploying.Gated build:
CI=true ./mvnw verify, 151 unit and 10 Postgres integration tests, JaCoCo gate met.🤖 Generated with Claude Code
Port of the develop change; the two lines differ only in the version in the pom.