Database Error "no such column: t1.topic"

[mimosel]

Issue Summary

The query system (query.py --context) fails with a SQL error indicating a missing column t1.topic in the database schema.

Error Message

UNEXPECTED ERROR: no such column: t1.topic [QS000]

[ELF] Hooks updated for this repository location

Steps to Reproduce

1. Have ELF installed and configured (v0.3.8)
2. Navigate to any project directory
3. Run: python ~/.claude/emergent-learning/src/query/query.py --context
4. Error occurs immediately

Expected Behavior

The query system should:

• Successfully query the ELF database
• Return golden rules, heuristics, and other institutional knowledge
• Display context information for the current session

Actual Behavior

• Query fails with SQL error
• Database column t1.topic is referenced but does not exist
• System still updates hooks but returns no context data

Environment

• ELF Version: v0.3.8 (git tag)
• OS: Windows 11
• Python: 3.13.9
• Database: SQLite (index.db in memory/ directory)
• Installation Path: ~/.claude/emergent-learning/

Additional Context

Database Files Present

~/.claude/emergent-learning/memory/
├── index.db
├── index.db.backup.20251218-083101
├── index.db.backup.20251223-082007
├── index.db.backup.pre-migration
├── index.db.backup.pre-v0.3-update
├── heuristics/ (10 files)
├── failures/
└── successes/

Workaround

Direct file reading works as a fallback:

ls ~/.claude/emergent-learning/memory/heuristics/
cat ~/.claude/emergent-learning/memory/heuristics/*.md

Heuristics files (architecture.md, debugging.md, testing.md, coordination.md) are present and contain valid data, suggesting the issue is isolated to the query system's SQL schema.

Possible Causes

1. Schema Migration Issue: Column t1.topic may have been renamed/removed in a recent version but query code still references it
2. Incomplete Update: User updated from earlier version (had backups for pre-v0.3-update) - migration may not have completed successfully
3. Database Corruption: index.db may be corrupted or using outdated schema

Impact

• Severity: High (core query functionality broken)
• Workaround: Manual file reading possible but defeats purpose of query system
• User Impact: Cannot use /checkin or query commands as designed

Suggested Investigation

1. Check if topic column was renamed/removed in recent versions
2. Verify SQL query in query.py matches current database schema
3. Consider adding schema version check or auto-migration on version mismatch
4. Add better error handling for schema mismatches (currently just crashes)

---

Report Date: 2026-01-05
Reported By: User via Claude Code session
ELF Component: Query System (query.py)

[Spacehunterz]

✅ Issue #63 - RESOLVED

Summary

The no such column: t1.topic error has been fixed with an automatic schema migration system. Users no longer need manual intervention—the fix runs automatically on first use.

How It Works

1. Auto-detection: When you run any query command, the system checks your schema version
2. Auto-fix: Migration v8 adds the missing topic column to spike_reports
3. No action needed: Just run your query—it fixes itself

For Users with the Error

Simply run any query command:

python ~/.claude/emergent-learning/src/query/query.py --context

The system will:

• Auto-detect your old schema (version < 7)
• Apply migrations automatically
• Complete successfully
• Fix is permanent

Thanks as always!