Skip to content

provider.md

Latest commit

 

History

History
83 lines (62 loc) · 2.52 KB

provider.md

File metadata and controls

83 lines (62 loc) · 2.52 KB
Raw

provider

Purpose

Stores the global registry of external data-provider namespaces used elsewhere in the schema.

Grain

One row per provider.

Live Stats

  • Snapshot source: data/pyvalue.db on 2026-07-28
  • Row count: 1
  • Table size: 4,096 bytes (4.0 KiB)
  • Approximate bytes per row: 4,096.0

Columns

Column Type Null Key Notes
provider_id INTEGER no PK surrogate key used by catalog FKs
provider_code TEXT no unique stable uppercase namespace; EODHD is the only registered provider
display_name TEXT no human-readable provider name
description TEXT yes optional provider summary
created_at TEXT no initial seed timestamp
updated_at TEXT no last metadata refresh timestamp

Keys And Relationships

  • Primary key: provider_id
  • Physical foreign keys: none
  • Physical references from other tables:
    • fx_refresh_state.provider -> provider_code
    • fx_supported_pairs.provider -> provider_code
    • provider_exchange.provider_id -> provider_id
    • provider_fx_rates.provider_id -> provider_id
  • Unique constraints beyond the primary key:
    • provider_code
  • Main logical refs: referenced physically by provider_exchange and provider_listing

Secondary Indexes

  • None beyond the primary key and unique constraints.

Main Read Paths

  • provider-code validation and id resolution before provider catalog writes
  • human-readable provider display in diagnostics

Main Write Paths

  • migration-time seed and future registry maintenance

Sample Rows

  • Snapshot source: data/pyvalue.db on 2026-07-28
  • Sample window: first 1 rows returned by SQLite ordered by provider_id ASC
[
  {
    "provider_id": 1,
    "provider_code": "EODHD",
    "display_name": "EODHD",
    "description": "Exchange, fundamentals, market-data, and FX provider.",
    "created_at": "2026-04-23T16:33:15.427807+00:00",
    "updated_at": "2026-07-11T14:03:20.673150+00:00"
  }
]

Review Notes

  • Keep this table narrow. Runtime config, API keys, rate limits, and provider capabilities belong outside this registry or in separate capability tables.