Schema version 1.1.0

meta.find_schema_problems() (09), the version row in the DDL (10), every
install running 00-10, and the removal of sql/migrate/ changed what a
complete database is. Databases from 1.0.0 are re-provisioned.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
peter 2026-10-06 11:20:51 +01:00
parent 1f5cfeceeb
commit 155fc7c3dd
3 changed files with 3 additions and 3 deletions

View file

@ -9,7 +9,7 @@ timeseries database. Both client libraries target the schema defined here:
Neither project should keep its own copy of the DDL. When the schema changes, Neither project should keep its own copy of the DDL. When the schema changes,
it changes **here**, and both projects re-provision / re-test against it. it changes **here**, and both projects re-provision / re-test against it.
Current schema version: **1.0.0** (see [`VERSION`](VERSION); recorded at runtime Current schema version: **1.1.0** (see [`VERSION`](VERSION); recorded at runtime
in the `meta.schema_version` table). in the `meta.schema_version` table).
--- ---

View file

@ -1 +1 @@
1.0.0 1.1.0

View file

@ -5,4 +5,4 @@
-- they were built for (Python: DB_SCHEMA_VERSION in tsapi_pgdb/_version.py). -- they were built for (Python: DB_SCHEMA_VERSION in tsapi_pgdb/_version.py).
INSERT INTO meta.schema_version (version, description) INSERT INTO meta.schema_version (version, description)
VALUES ('1.0.0', 'Initial schema'); VALUES ('1.1.0', 'meta.find_schema_problems(); every install runs 00-10');