ID |
|
|---|---|
Status |
Backlog |
Bucket |
feature |
Theme |
routine |
Created |
2026-07-08 |
Updated |
2026-07-08 |
Routine chains: remaining fetch-form breadth
R435 shipped order-significant @routine / @reference composition end to end for the core
surface: every chain shape at root and child positions, the inline correlated multiset, and the
@splitQuery batched keyed re-query on table-backed parents (batch key = the routine’s
column-bound inputs). Four fetch-form extensions were left as typed Deferred landings whose
planSlug points here; each falls on an existing model seam, so they slice independently:
-
Chains with more than one routine node (root and child alike): the multi-lateral emit. Classification and validation already handle the shape; the emitters need the second (and later)
CROSS JOIN LATERALpositions, which the forward join walks inInlineTableFieldEmitterandSplitRowsMethodEmitterare already shaped for. -
@lookupKeycomposition on routine-backed children (theSplitLookupTableFieldlanding). -
Record-backed parents (
RecordTableFieldseam): a routine child under a@record/ service-produced parent, wherecolumnMappingbinds against the record’s accessors rather than a catalog table (RoutineDirectiveResolver’s null-previous-node `Deferredcovers this today). -
TableInterfaceTypeparents (theInterfaceFieldseam).
Also parked here: Connection pagination over a catalog-terminus chain containing a routine
node (typed Deferred with empty planSlug in R435; adopt it here or leave it unfiled until
someone asks).