📄 tanstack/db/latest/docs/reference/interfaces/Context

File: Context.md | Updated: 11/15/2025

Source: https://tanstack.com/db/latest/docs/reference/interfaces/Context



TanStack

DB v0v0

Search...

+ K

Auto

Log In

TanStack StartRC

Docs Examples GitHub Contributors

TanStack Router

Docs Examples GitHub Contributors

TanStack Query

Docs Examples GitHub Contributors

TanStack Table

Docs Examples Github Contributors

TanStack Formnew

Docs Examples Github Contributors

TanStack DBbeta

Docs Github Contributors

TanStack Virtual

Docs Examples Github Contributors

TanStack Paceralpha

Docs Examples Github Contributors

TanStack Storealpha

Docs Examples Github Contributors

TanStack Devtoolsalpha

Docs Github Contributors

More Libraries

Maintainers Partners Support Learn StatsBETA Discord Merch Blog GitHub Ethos Brand Guide

Documentation

Framework

React logo

React

Version

Latest

Search...

+ K

Menu

Getting Started

Guides

Collections

Frameworks

Community

API Reference

Framework

React logo

React

Version

Latest

Menu

Getting Started

Guides

Collections

Frameworks

Community

API Reference

On this page

Context

Copy Markdown

Interface: Context
==================

Defined in: packages/db/src/query/builder/types.ts:35

Context - The central state container for query builder operations

This interface tracks all the information needed to build and type-check queries:

Schema Management:

  • baseSchema: The original tables/collections from the from() clause
  • schema: Current available tables (expands with joins, contracts with subqueries)

Query State:

  • fromSourceName: Which table was used in from() - needed for optionality logic
  • hasJoins: Whether any joins have been added (affects result type inference)
  • joinTypes: Maps table aliases to their join types for optionality calculations

Result Tracking:

  • result: The final shape after select() - undefined until select is called

The context evolves through the query builder chain:

  1. from() sets baseSchema and schema to the same thing
  2. join() expands schema and sets hasJoins/joinTypes
  3. select() sets result to the projected shape

Properties
----------
### baseSchema

ts

baseSchema: ContextSchema;


baseSchema: ContextSchema;

Defined in: packages/db/src/query/builder/types.ts:37


### fromSourceName

ts

fromSourceName: string;


fromSourceName: string;

Defined in: packages/db/src/query/builder/types.ts:41


### hasJoins?

ts

optional hasJoins: boolean;


optional hasJoins: boolean;

Defined in: packages/db/src/query/builder/types.ts:43


### joinTypes?

ts

optional joinTypes: Record<string, "inner" | "left" | "right" | "full" | "outer" | "cross">;


optional joinTypes: Record<string, "inner" | "left" | "right" | "full" | "outer" | "cross">;

Defined in: packages/db/src/query/builder/types.ts:45


### result?

ts

optional result: any;


optional result: any;

Defined in: packages/db/src/query/builder/types.ts:50


### schema

ts

schema: ContextSchema;


schema: ContextSchema;

Defined in: packages/db/src/query/builder/types.ts:39


### singleResult?

ts

optional singleResult: boolean;


optional singleResult: boolean;

Defined in: packages/db/src/query/builder/types.ts:52

Edit on GitHub

Home

Partners Become a Partner

Code RabbitCode Rabbit CloudflareCloudflare AG GridAG Grid NetlifyNetlify NeonNeon WorkOSWorkOS ClerkClerk ConvexConvex ElectricElectric SentrySentry PrismaPrisma StrapiStrapi UnkeyUnkey

scarf analytics