Commands › Snapshot / Staging › Snapshot Staging Migrate Database Schema
Snapshot Staging Migrate Database Schema
Coming soon
Before you run this
Local snapshot staging database file present (default %LOCALAPPDATA%\Adelphos\Snapshot\staging.db). Migration pack ships with the plug-in.
After it runs
The staging database schema is at the latest version recorded in the migration pack; pending migrations applied in order; schema version row updated.
When to use this
- Plug-in upgrade — a new release adds columns to the snapshot staging tables and you want the existing staging DB upgraded so old projects keep working without losing their staged data.
Don't use this when
Resetting / wiping staging data (use the staging cleanup command), upgrading the Supabase snapshot tables (server-side migrations), or first-run database creation (handled at install).
Decision flow
1. Open the local staging SQLite database. 2. Read the current schema version row. 3. Apply each pending migration in order from the migration pack. 4. Update the schema version row to the latest applied migration. 5. Report from-version, to-version and migration count.
What you'll see in the chat
on start
I'll migrate the snapshot staging database to the latest schema now.
thinking
Applying pending migrations in order to the local staging DB.
on success
Done — staging DB migrated from v{from_version} to v{to_version} ({n_migrations} migrations applied).
on failure
Couldn't migrate the staging schema: {error}.
REST API
Not yet exposed
This command does not carry a [RestApi] attribute today. Once tagged, this section will auto-populate with:
POST /api/v1/commands/snapshot_staging_migrate_database_schema- Request body schema (from
[RestApiParam]) - Response schema (from
[RestApiResponse]) - curl / JS / Python code examples
Keywords & intent patterns
snapshot staging migration · schema upgrade · staging database · plug-in upgrade · snapshot DB
Related
| Pillar | Snapshot / Staging |
|---|