Skip to content

Add schema versioning to the local SQLite stores #4832

Description

@JSONbored

Problem: Every one of the miner's local SQLite stores only ever does CREATE TABLE IF NOT EXISTS — there's no user_version/migration mechanism at all, unlike the main product's migrations/ discipline.

Area: AMS / Miner

Proposal: Add a lightweight schema-version column and migration-runner convention shared across all the miner's local stores.

Deliverables:

  • A schema-versioning convention applied consistently across every store.

Acceptance criteria:

  • Opening an older-schema database file triggers a migration rather than silent incompatibility or data loss.

Boundaries:

  • Keep it lightweight — this doesn't need the full weight of the main product's migration tooling, just a real version check.

Metadata

Metadata

Assignees

No one assigned

    Labels

    gittensor:featureGittensor-scored feature linked to a feature issue — scores a 0.25x multiplier.help wantedExtra attention is needed

    Projects

    Status
    In Progress

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions