DatabaseMigrator

Controls how migrations handle foreign keys constraints.

When the eraseDatabaseOnSchemaChange flag is true, the migrator will automatically wipe out the full database content, and recreate the whole database from scratch, if it detects that a migration has changed its definition.

This flag can destroy your precious users’ data!

But it may be useful in two situations:

1. During application development, as you are still designing migrations, and the schema changes often.

   In this case, it is recommended that you make sure this flag does not ship in the distributed application, in order to avoid undesired data loss:

   var migrator = DatabaseMigrator()
   #if DEBUG
   // Speed up development by nuking the database when migrations change
   migrator.eraseDatabaseOnSchemaChange = true
   #endif
   

2. When the database content can easily be recreated, such as a cache for some downloaded data.

A new migrator.

Returns a migrator that will not perform deferred foreign key checks in all newly registered migrations.

The returned migrator is unsafe, because it no longer guarantees the integrity of the database. It is your responsibility to register migrations that do not break foreign key constraints.

Running migrations without foreign key checks can improve migration performance on huge databases.

Example:

var migrator = DatabaseMigrator()
migrator.registerMigration("A") { db in
    // Runs with deferred foreign key checks
}
migrator.registerMigration("B", foreignKeyChecks: .immediate) { db in
    // Runs with immediate foreign key checks
}

migrator = migrator.disablingDeferredForeignKeyChecks()
migrator.registerMigration("C") { db in
    // Runs with disabled foreign key checks
}
migrator.registerMigration("D", foreignKeyChecks: .immediate) { db in
    // Runs with immediate foreign key checks
}

Registers a migration.

migrator.registerMigration("createAuthors") { db in
    try db.create(table: "author") { t in
        t.autoIncrementedPrimaryKey("id")
        t.column("creationDate", .datetime)
        t.column("name", .text).notNull()
    }
}

Iterate migrations in the same order as they were registered. If a migration has not yet been applied, its block is executed in a transaction.

Iterate migrations in the same order as they were registered. If a migration has not yet been applied, its block is executed in a transaction.

Experimental

Iterate migrations in the same order as they were registered, up to the provided target. If a migration has not yet been applied, its block is executed in a transaction.

Iterate migrations in the same order as they were registered, up to the provided target. If a migration has not yet been applied, its block is executed in a transaction.

Experimental

Iterate migrations in the same order as they were registered. If a migration has not yet been applied, its block is executed in a transaction.

The list of registered migration identifiers, in the same order as they have been registered.

Returns the identifiers of registered and applied migrations, in the order of registration.

See also appliedIdentifiers(_:).

Returns the applied migration identifiers, even unregistered ones.

See also appliedMigrations(_:).

Returns the identifiers of completed migrations, of which all previous migrations have been applied.

Returns true if all migrations are applied.

Returns whether database contains unknown migration identifiers, which is likely the sign that the database has migrated further than the migrator itself supports.

Returns a Publisher that asynchronously migrates a database.

let migrator: DatabaseMigrator = ...
let dbQueue: DatabaseQueue = ...
let publisher = migrator.migratePublisher(dbQueue)

It completes on the main dispatch queue.

Returns a Publisher that asynchronously migrates a database.

let migrator: DatabaseMigrator = ...
let dbQueue: DatabaseQueue = ...
let publisher = migrator.migratePublisher(dbQueue, receiveOn: DispatchQueue.global())

It completes on scheduler.