Skip to content

br 0.1.20: DATABASE_ERROR 'no such column: source_system in table issues' on older databases #104

@w3dev33

Description

@w3dev33

Description

br 0.1.20 fails with DATABASE_ERROR when running br list on databases created with older versions of br (e.g. 0.1.14). The error does not occur with br 0.1.14.

Error

{
  "error": {
    "code": "DATABASE_ERROR",
    "message": "Database error: internal error: no such column: source_system in table issues",
    "hint": null,
    "retryable": false,
    "context": null
  }
}

Reproduction

  1. Create a workspace with br 0.1.14 and add some issues
  2. Upgrade to br 0.1.20
  3. Run br list in that workspace → DATABASE_ERROR

Investigation

  • The source_system column does exist in the issues table (verified via PRAGMA table_info(issues) and direct SELECT source_system FROM issues LIMIT 1)
  • br doctor passes all checks including schema.columns and sqlite.integrity_check
  • The error is specific to br list (and likely other commands that read issues)
  • The issue appears related to the fsqlite update in 0.1.20 — databases created with older br versions have a different column order in the issues table

Affected commands

  • br list
  • Likely any command that queries the issues table via fsqlite

Workaround

Downgrade to br 0.1.14:

curl -fsSL https://raw.githubusercontent.com/Dicklesworthstone/beads_rust/main/install.sh | bash -s -- --version v0.1.14

Environment

  • macOS ARM64 (Apple Silicon)
  • br 0.1.20 (darwin_arm64)
  • Database created with br 0.1.14

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions