DATA-004 follow-up: capture legacy schema patches as migration 0002 #241
Labels
No labels
blocked:children
blocked:commit-ready-failed
blocked:depends-231
blocked:depends-236
blocked:depends-237
blocked:depends-238
blocked:depends-239
blocked:gate-fetch
blocked:gate-fetch
blocked:gate-lint
blocked:gate-research
blocked:needs-attention
blocked:needs-decision
blocked:no-changes
blocked:no-procedure
blocked:preflight
blocked:verify-failed
bug
enhancement
feature-request
high-priority
in-progress
lint-cleanup
needs-decompose
needs-triage
ops-retry
ops-task
phase-5
quickfix
security/medium
self-building
triage-approved
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Mark/mesh-seed#241
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Background
DATA-004 (Issue #166) implemented a versioned migration framework (MigrationRunner), but the initial
0001_initial_schemamigration only captures the base schema DDL. Several ad-hoc schema patches that were previously applied viaSchemaManager._add_column_if_missing()are not yet captured as versioned migrations.Known missing patches
agents.embeddingcolumn (added for semantic search)_add_column_if_missing()calls in the oldschema.pytransactions.storage_duration_dayscolumnAcceptance criteria
_add_column_if_missingcalls from the oldsubstrate/ledger/schema.py(git show HEAD~1:substrate/ledger/schema.py | grep _add_column_if_missing)substrate/ledger/migrations.pypytest tests/unit/test_embedding_ledger.py -x -qpasses