Member Junction
    Preparing search index...

    Interface QueryCacheAuthorization

    Result of ProviderBase.ResolveQueryCacheAuthorization — the single pre-fingerprint resolution + authorization computation the RunQuery TTL cache gate relies on (B45/B46). See the method JSDoc for the full contract.

    interface QueryCacheAuthorization {
        authorized: boolean;
        categoryPath?: string;
        contextTokens?: (
            | "Context.UserID"
            | "Context.UserEmail"
            | "Context.UserName"
            | "Context.Now"
            | "Context.Today"
            | "Context.StartOfWeek"
            | "Context.StartOfMonth"
            | "Context.StartOfQuarter"
            | "Context.StartOfYear"
        )[];
        definition?: QueryDefinitionSignature;
        fieldSecurityKey?: string;
        queryId?: string;
        queryName?: string;
        resolvable: boolean;
    }
    Index

    Properties

    authorized categoryPath? contextTokens? definition? fieldSecurityKey? queryId? queryName? resolvable

    Properties

    authorized: boolean

    The user may run the resolved query. Meaningful only when resolvable is true.

    categoryPath?: string

    Canonical full category path of the RESOLVED query (e.g. '/MJ/AI/Agents/'; '' when uncategorized).

    contextTokens?: (
        | "Context.UserID"
        | "Context.UserEmail"
        | "Context.UserName"
        | "Context.Now"
        | "Context.Today"
        | "Context.StartOfWeek"
        | "Context.StartOfMonth"
        | "Context.StartOfQuarter"
        | "Context.StartOfYear"
    )[]

    The context tokens the resolved query's template reads, with every query it composes (FindQueryContextTokens). Their values join the fingerprint, so a result that depends on the user or the date is never served to another user or on another day.

    definition?: QueryDefinitionSignature

    The definition the provider would execute on a miss. Set by providers that execute queries themselves; a slot written under another definition is then a miss. Undefined where the provider cannot compute one (a client, whose slots the server validates instead).

    fieldSecurityKey?: string

    The user's field-security profile (FieldSecuritySQLGate.CatalogDenialProfileKey) when the run drops denied columns from its rows; it joins the fingerprint, so users with different denials never share a slot. Undefined when the rows are the same for every authorized user.

    queryId?: string

    Resolved query ID. With queryName, the identity the RunQuery fingerprint is built from, so a request by ID, by name, or by both reaches the same slot.

    queryName?: string

    Resolved query name — for log messages when the request was by ID only.

    resolvable: boolean

    Metadata could resolve the request (by ID, or by name [+ stated category]).

    Settings

    Member Visibility

    On This Page

    Properties