Schema Reference

The nbadb analytical surface exposes public tables and views across dimensions, facts, bridges, derived aggregations, and analytics views.

Treat this section like the warehouse playbook: the curated pages explain how the lineup fits together, while the generated reference pages give you the box-score-exact schema contracts when you need to check a column, key, or constraint at 2am.

Work the section in three possessions

1. Choose the family. Start on the curated guides when you still need judgment about grain, surface, or whether a shortcut already exists.
2. Lock the join lane. Switch to Relationships once you know the tables but want the cleanest path between them.
3. Verify the contract. Finish on Raw Reference, Staging Reference, or Star Reference when the question turns into exact columns, types, or nullability.

Choose the right route

Know which page owns which job

Choose your first pass

If you only remember one decision tree, use this one.

flowchart TD
    Start["Question in hand"] --> Family{"Still choosing the table family?"}
    Family -- Yes --> Curated["Curated family pages"]
    Family -- No --> Join{"Need the safest join lane?"}
    Join -- Yes --> Relationships["Relationships"]
    Join -- No --> Exact{"Need exact columns or nullability?"}
    Exact -- Yes --> Generated["Raw / Staging / Star Reference"]
    Exact -- No --> Curated
    style Curated fill:#e8f5e9
    style Relationships fill:#fff3e0
    style Generated fill:#e1f5fe

Text fallback: start on the curated family pages when you still need judgment, jump to Relationships when the join lane is the real question, and finish on the generated references when exact contracts matter.

Start by the handle you already have

Read the jersey prefix

Warehouse offensive system

• Star first: dimensions create stable context around fact grains so common queries stay join-friendly.
• History where it matters: dim_player and dim_team_history use SCD Type 2 semantics for time-aware identity tracking.
• Conformed anchors: player_id, team_id, game_id, and season_year do most of the passing across the model.
• Smallest useful grain: start at the narrowest fact that answers the question, then climb to agg_ or analytics_ only when the use case repeats.

Generated tier references

Regenerate the command-owned reference pages with:

uv run nbadb docs-autogen --docs-root docs/content/docs

That command owns the raw, staging, and star reference artifacts. Keep this index, the family guides, and Relationships curated.