General Discussion

[zhouji1026]

Self Checks

• I have searched for existing issues search for existing issues, including closed ones.
• I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
• [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:)
• Please do not modify this template :) and fill in all the required fields.

Content

providers
provider_models
provider_orders
provider_model_settings
provider_model_credentials
provider_credentials
May I ask what the relationship is between these tables?

[dosubot[bot]]

Here's the relationship between these tables:

providers — The core table representing configured API providers for a tenant. It tracks provider type (custom/system), validity, quota info, and references a credential via credential_id → provider_credentials.id. [1]

provider_credentials — Stores encrypted provider-level credentials (shared across all models of that provider). Supports multiple named credentials per provider for credential pooling. [2]

provider_models — Defines specific models available from a provider (e.g., gpt-4, gpt-3.5-turbo). References a model-specific credential via credential_id → provider_model_credentials.id. [3]

provider_model_credentials — Stores encrypted credentials specific to individual models (as opposed to provider-wide credentials). Supports multiple named credentials per model for load balancing. [4]

provider_model_settings — Per-model configuration like enabled/disabled state and load balancing toggle. Logically related to provider_models via (tenant_id, provider_name, model_name, model_type). [5]

provider_orders — Tracks payment transactions for provider quota purchases. Logically related to providers via (tenant_id, provider_name). [6]

Key relationships:

graph TD
    PC["provider_credentials"] -->|"credential_id (FK)"| P["providers"]
    P -->|"logical: tenant_id + provider_name"| PM["provider_models"]
    P -->|"logical: tenant_id + provider_name"| PO["provider_orders"]
    PMC["provider_model_credentials"] -->|"credential_id (FK)"| PM
    PMS["provider_model_settings"] -->|"logical: tenant_id + provider_name + model"| PM

Loading

The design uses two-level credential management: provider-level credentials (provider_credentials) shared across all models, and model-level credentials (provider_model_credentials) for per-model configuration. Explicit foreign keys exist only for the credential references; other relationships are logical via composite keys like (tenant_id, provider_name) without database-level FK constraints [7].

To reply, just mention @dosu.

---

Share context across your team and agents. Try Dosu.