Member Junction
    Preparing search index...

    Pipeline trace capturing the SQL state after each pass. Used for error diagnosis — when the database rejects the output, the caller can see what each pass produced.

    Composition renders first, then composes: the outer template renders once, each composed query instance renders on its own (Instances), and the plain SQL is assembled from them.

    interface RenderTrace {
        AfterComposition: string;
        AfterPaging: string | null;
        AfterTemplates: string;
        CompositionDiagnostics: CompositionDiagnostic[];
        Instances: RenderInstanceTrace[];
    }
    Index

    Properties

    AfterComposition: string

    The assembled SQL: every template rendered, every composition emitted as a CTE. For a query without compositions, its rendered SQL. Before row caps and paging.

    AfterPaging: string | null

    SQL after paging (final) — only set if paging was applied

    AfterTemplates: string

    The fully resolved, executable SQL before row caps and paging: the same text as AfterComposition. Authorization checks read it, so it always holds every composed query.

    CompositionDiagnostics: CompositionDiagnostic[]

    Composition metadata: which deps resolved, which CTEs generated

    Instances: RenderInstanceTrace[]

    Each composed query instance, dependencies first. Empty when the query composes nothing.