peter
cddaec5730
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>
8 lines
531 B
SQL
8 lines
531 B
SQL
-- ============================================================================
|
|
-- Schema version row -- runs last, so a database that has it is complete.
|
|
-- ============================================================================
|
|
-- Keep this string equal to ../VERSION. Clients compare it with the version
|
|
-- they were built for (Python: DB_SCHEMA_VERSION in tsapi_pgdb/_version.py).
|
|
|
|
INSERT INTO meta.schema_version (version, description)
|
|
VALUES ('1.4.0', 'meta.sessions.json dropped: the definition is the only schedule');
|