{#if !hideTrigger} {/if} {#snippet headerLeft()} Each schema edit made in the database manager is captured here as a migration. Tracking schema changes as migrations makes it easy to export data tables to other workspaces, and to reproduce their schema when forking a workspace. {/snippet} {#snippet headerRight()} {#if enabled && canManage} disableMigrations() } ]} > {#snippet buttonReplacement()} {/if} {:else} {#if loadError}
Could not read applied status from the data table: {loadError}
{/if}
{#if migrations.length === 0}
{generatingInitial ? 'Snapshotting current schema…' : 'No migrations yet'}
{:else} {#each migrations as m (m.timestamp)}
{#if m.schemas} {#each m.schemas as s (s)} {s} {/each} {:else} whole database {/if}
{/each} {/if}
{/if}
(newMigrationOpen = false)} onSeeMigration={(m) => openMigration(m.timestamp)} /> {#if viewMigration}
{viewMigration.timestamp} {#snippet content()} {#if viewMigration?.code_down}
{:else if addingDown}
{:else}
No down migration
{/if}
{/snippet}
{/if}

"{deleteTarget?.name}" is installed on the data table. Revert it first to undo its schema change, or delete only the definition and leave the schema as-is — deleting without reverting means it can no longer be reverted.