pf_app
Paul Trowbridge
0fdb08291d
The bridge builds its own view from the pivot's filters, and those filters can name pf_bucket_ord or pf_segment_ord — columns that exist only as expressions. A view created without them cannot resolve the column, so the bridge failed outright as soon as anyone filtered on an ordering column. The per-slice path is left alone: its filters are built from col_meta names, so they only ever reference real columns. Said so in place, since the asymmetry otherwise reads as an oversight. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| lib | ||
| public | ||
| routes | ||
| setup_sql | ||
| ui | ||
| .env.example | ||
| .gitignore | ||
| CLAUDE.md | ||
| install.sh | ||
| package-lock.json | ||
| package.json | ||
| PERSPECTIVE.md | ||
| pf_perspective_options.md | ||
| pf_spec.md | ||
| pf.sh | ||
| server.js | ||