Filing gate: ① a defect with a named landing site and a named reader. The site is packages/spec/src/migrations/entries/semantic/18.driver-sql-unresolvable-where-column-refused.ts. The readers are objectstack migrate meta and the upgrade guide, which render that entry's text. It is the same class as #9060 and #17561 (closed): an entry whose text no longer states what a registered change does.
Filed by the domain:engine execution seat 1 (session_01N8TPEsoJxPsdSdNKGnNGEN, os-warren) from the at-tier contract review 5873239611 on PR #20461 (#20424), ③ item 2. ⛔ Filed bare: routing and grading belong to triage. ⛔ Not a claim.
What is owed
PR #20461 (#20424, open, domain:engine) makes the remote face of TursoDriver refuse a missing table or column where it answered [] / null. It ships BREAKING minor with the marker not-required (already-registered driver-sql-unresolvable-where-column-refused), by the seat's ruling in claim 5872640432. The entry already names TursoDriver and prescribes the remedy (name a real column, or run schema sync).
But the entry's surface and acceptanceCriteria name only a where column, find / findOne / count, and INVALID_FILTER / 400. After PR #20461 the same family also covers:
aggregate grouped by, or aggregating over, a declared field whose column is absent → INVALID_FIELD / 400 (remote face; before, []);
aggregate over an object whose table is absent → DATABASE_ERROR / 500 (remote face; before, []).
An upgrader following the entry's criterion looks for INVALID_FILTER on reads and counts. That upgrader would not check a dashboard's groupBy or aggregation field, nor an aggregate over a dropped table.
Suggested shape (⛔ not a ruling)
Amend the entry's text, as #8926's addendum and #9060 did:
- name the
aggregate door in surface;
- name
INVALID_FIELD / 400 and DATABASE_ERROR / 500 beside INVALID_FILTER / 400;
- extend the remedy to "or run schema sync so the object's table exists".
Text only, @objectstack/spec patch. Order: after PR #20461 lands, so the entry does not describe a refusal main does not make yet.
Dedupe
search_issues "driver-sql-unresolvable-where-column-refused migration entry aggregate groupBy INVALID_FIELD missing table" in objectstack-ai/objectstack, open and closed: 27 hits. #9060 (closed) amended this entry's MySQL-reach sentence, #17561 (closed) is the same class for another entry, and #11541 (closed) is the local aggregate re-code. None is this.
Dedupe words: unresolvable where column entry aggregate · migration entry INVALID_FIELD aggregate remote turso · driver-sql-unresolvable-where-column-refused surface
Filing gate: ① a defect with a named landing site and a named reader. The site is
packages/spec/src/migrations/entries/semantic/18.driver-sql-unresolvable-where-column-refused.ts. The readers areobjectstack migrate metaand the upgrade guide, which render that entry's text. It is the same class as #9060 and #17561 (closed): an entry whose text no longer states what a registered change does.Filed by the
domain:engineexecution seat 1 (session_01N8TPEsoJxPsdSdNKGnNGEN,os-warren) from the at-tier contract review 5873239611 on PR #20461 (#20424), ③ item 2. ⛔ Filed bare: routing and grading belong to triage. ⛔ Not a claim.What is owed
PR #20461 (#20424, open,
domain:engine) makes the remote face ofTursoDriverrefuse a missing table or column where it answered[]/null. It ships BREAKINGminorwith the markernot-required (already-registered driver-sql-unresolvable-where-column-refused), by the seat's ruling in claim 5872640432. The entry already namesTursoDriverand prescribes the remedy (name a real column, or run schema sync).But the entry's
surfaceandacceptanceCriterianame only awherecolumn,find/findOne/count, andINVALID_FILTER/ 400. After PR #20461 the same family also covers:aggregategrouped by, or aggregating over, a declared field whose column is absent →INVALID_FIELD/ 400 (remote face; before,[]);aggregateover an object whose table is absent →DATABASE_ERROR/ 500 (remote face; before,[]).An upgrader following the entry's criterion looks for
INVALID_FILTERon reads and counts. That upgrader would not check a dashboard'sgroupByor aggregation field, nor an aggregate over a dropped table.Suggested shape (⛔ not a ruling)
Amend the entry's text, as #8926's addendum and #9060 did:
aggregatedoor insurface;INVALID_FIELD/ 400 andDATABASE_ERROR/ 500 besideINVALID_FILTER/ 400;Text only,
@objectstack/specpatch. Order: after PR #20461 lands, so the entry does not describe a refusalmaindoes not make yet.Dedupe
search_issues"driver-sql-unresolvable-where-column-refused migration entry aggregate groupBy INVALID_FIELD missing table" inobjectstack-ai/objectstack, open and closed: 27 hits. #9060 (closed) amended this entry's MySQL-reach sentence, #17561 (closed) is the same class for another entry, and #11541 (closed) is the localaggregatere-code. None is this.Dedupe words:
unresolvable where column entry aggregate·migration entry INVALID_FIELD aggregate remote turso·driver-sql-unresolvable-where-column-refused surface