The definition string is the only stored schedule. The "json" column held a
parsed copy that the Python client wrote, the C++ client never wrote, and
neither client read -- and a raw UPDATE of one field silently left two
different schedules. Clients derive the parsed form from the definition.
09_schema_check.sql no longer expects the column; VERSION and
10_schema_version.sql at 1.4.0. Re-provision databases (no migrations).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- meta.series_schemas (name, description, created_at, created_by), seeded
with 'series'. FK series_db_schema_fkey from meta.series.db_schema: a
series may only live in a registered schema, for every client.
Unregistered schemas belong to the user and are never touched.
- CHECK series_schemas_name_check and series_table_name_check enforce the
shared lower-case identifier rule in the database.
- meta.find_schema_problems() covers the registry and reports a registered
schema that no longer exists; user schemas are not examined.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Single source of truth for the timeseries PostgreSQL schema shared by the
Python (TSAPI_SERIESDB_PG_PY) and C++ (TSAPI_POSTGRES_CPP) libraries. SQL
seeded byte-for-byte from TSAPI_SERIESDB_PG_PY/tsapi_pgdb/sql on 2026-09-02.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
