Expand description
Composite document queries — the client half of “a page plus the sub-queries derived from it”, answered as ONE merged proof.
Attach sub-queries directly to DocumentQuery with an explicit
page limit, then fetch the result as [CompositeDocuments].
Each CompositeSubQuery is a by-id join, an indexed lookup, a
grouped count, or an independent sibling, whose IN clause the
server derives from the proven page (or an earlier documents
sub-query) — the request never names the derived values, so the
responding node cannot steer them. The verifier bootstraps the page
from the merged proof and re-derives every sub-query with the same
builders, so a substituted, omitted or injected sub-result fails
verification. See drive::query::composite_document_query
for the shape rules and the trust model.
Structs§
- Composite
Binding - The derived clause of a sub-query:
<field> IN <values>, where the values are read off the source’s proven documents. - Composite
SubQuery - One sub-query of a composite request.
Enums§
- Composite
Binding Source - Whose proven documents a sub-query’s values are read from.
- Composite
SubQuery Kind - What a sub-query returns.