pt/pf_app
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Drop point-in-time counts and a temporary table name from CLAUDE.md

Browse Source 
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This commit is contained in:
Paul Trowbridge 2026-09-25 00:16:50 -04:00
parent 82fa560cc8
commit 6deb8e547c
1 changed files with 4 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
CLAUDE.md
View File

@ -188,11 +188,9 @@ constant — read through a join on `pf.version`. That made the pivot the only
reader that knew what bucket a row was in. The same CASE was copied into reader that knew what bucket a row was in. The same CASE was copied into
`/agg`, the `/data` cursor and `rlarp.load_osm_pf` in `/opt/forecast`, and any `/agg`, the `/data` cursor and `rlarp.load_osm_pf` in `/opt/forecast`, and any
direct query had to copy it again. It also meant editing a version's fallback direct query had to copy it again. It also meant editing a version's fallback
name silently renamed every past adjustment. The 2026-09-24 backfill in name silently renamed every past adjustment. The backfill in
`setup_sql/01_schema.sql` stamped the existing entries with that rule; before it `setup_sql/01_schema.sql` stamped the existing entries with that rule.
ran, the pre-backfill `label`/`bucket` values were saved to `pf.version.unlabeled_load` is read by nothing now; the column remains.
`pf.bak_log_names_20260924`. `pf.version.unlabeled_load` is read by nothing now;
the column remains.
**What this replaced.** The prefix used to be computed client-side, as **What this replaced.** The prefix used to be computed client-side, as
Perspective expression columns (`pf_bucket_ord`, `pf_segment_ord`) built from Perspective expression columns (`pf_bucket_ord`, `pf_segment_ord`) built from
@ -764,8 +762,7 @@ the negative rows stay where the business was — so a shifted recode is a timin
move (pull forward, push out), and with a shift `set` may be empty. The moved move (pull forward, push out), and with a shift `set` may be empty. The moved
rows' period dimensions are re-derived from `pf.dim_period` against the shifted rows' period dimensions are re-derived from `pf.dim_period` against the shifted
date, as clone's are; a row whose date is null keeps the label it had, since a date, as clone's are; a row whose date is null keeps the label it had, since a
calendar lookup on nothing would blank it (v34 has 1,033 baseline rows with no calendar lookup on nothing would blank it. Without a shift nothing is derived and recode copies as it always
`sdate_e`). Without a shift nothing is derived and recode copies as it always
did. Clone still blanks those labels on a null date; it has not been changed. did. Clone still blanks those labels on a null date; it has not been changed.
`build_where()` validates every slice key against col_meta (only `role = dimension` allowed). Values are escaped but not parameterized — consistent with existing patterns, debuggable in pg logs. `build_where()` validates every slice key against col_meta (only `role = dimension` allowed). Values are escaped but not parameterized — consistent with existing patterns, debuggable in pg logs.