pf_app/setup_sql
Paul Trowbridge 98322a6080 Close the write-only surface left behind by the ordinals
bucket_order and log.seq were still settable -- PUT /versions/:id took the
first, PATCH /log/:logid the second -- with nothing left to read either. A
field that only ever gets written is worse than a missing one: the call
succeeds, so the caller has no way to find out it did nothing.

The columns themselves stay, marked vestigial where they are declared.
Dropping a column is not worth a migration to reclaim two that cost nothing.

pf.log.bucket is untouched and stays exactly as it was -- what a row counts
toward, read first by BUCKET_EXPR. It is the bucket *order* that no longer
needs storing, the text having become the order.

Also removes a comment head in Forecast.jsx that survived its function and
had glued itself onto fitColumns.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-09-17 22:51:34 -04:00
..
01_schema.sql Close the write-only surface left behind by the ordinals 2026-09-17 22:51:34 -04:00
02_auth.sql Put the app behind a login 2026-09-14 22:20:25 -04:00
gen_dim_period.sql Add dim_group to col_meta and pf.dim_period calendar table 2026-05-23 01:46:16 -04:00