meta

The meta table contains exactly one row. It describes the dataset artifact, its owning Job, immediate continuation lineage, schema and engine versions, provider provenance, requested coverage, written History coverage, and quality summary.

Identity and lineage

Column Type Meaning
dataset_id TEXT Canonical Dataset UUID, generated independently from the Job ID
parent_dataset_id TEXT NULL Immediate source Dataset UUID for Continue in New Job; otherwise NULL
job_id TEXT Canonical owning Job UUID
parent_job_id TEXT NULL Immediate source Job UUID for a continuation; otherwise NULL
job_name TEXT Owning Job name snapshot
parent_job_name TEXT NULL Immediate parent Job name snapshot; otherwise NULL

Nested continuations form an immediate-parent chain. Follow parent_dataset_id repeatedly to reconstruct it; do not use display names or ShortIDs as join keys.

Version columns

Column Type Values and conditions
schema_version INTEGER 8 for current newly created datasets
app_version TEXT DataCat app version that created the artifact
app_build TEXT DataCat app build identifier
provider_api_version TEXT NULL Provider API/version context when available
indicator_registry_version TEXT NULL Registry version; NULL without indicators
indicator_engine TEXT NULL Calculation engine identity; NULL without indicators
indicator_engine_version TEXT NULL Calculation engine version; NULL without indicators

Job configuration

Column Type Values and conditions
provider TEXT Canonical provider identity
venue TEXT Canonical venue identity, even when the UI omits a redundant selector
symbol TEXT Provider symbol selected by the Job
timeframe TEXT Job timeframe
mode TEXT history, live, or history_plus_live
warmup_bars INTEGER Required warmup coverage for the frozen Job configuration
indicator_table_count INTEGER Actual number of allocated indicator output tables; 0 without indicators

Quality and coverage

gaps_remaining counts persisted gaps rows whose status is not resolved. It includes pending, open, and exhausted rows and is not the same as a provider-policy-filtered app presentation such as Open Gaps.

The canonical computation timestamps are integer milliseconds. Matching UTC text columns exist for manual inspection:

Milliseconds UTC text Nullable condition
created_at_ms created_at_utc Never
requested_start_ms requested_start_utc Can be NULL only when no start boundary applies
requested_end_ms requested_end_utc NULL for open-ended Live and History + Live
history_written_start_ms history_written_start_utc NULL in pure Live mode
history_written_end_ms history_written_end_utc NULL in pure Live mode

Search documentation

Search across 46 documentation pages.