Drivers

db-migrate talks to databases through drivers, installed next to db-migrate and selected by the driver setting of an environment.

Database	Package	driver	Page
PostgreSQL	db-migrate-pg	pg, postgres, postgresql	PostgreSQL
MySQL, MariaDB	db-migrate-mysql	mysql	MySQL
SQLite	db-migrate-sqlite3	sqlite3, sqlite	sqlite3
CockroachDB	db-migrate-cockroachdb	cockroachdb	CockroachDB
MongoDB	db-migrate-mongodb	mongodb	MongoDB

Any other driver is loaded as db-migrate-<driver>, or from a path with "driver": { "require": "./my-driver" }.

Features

	pg	mysql	sqlite3	cockroachdb	mongodb
Migration lock	since 1.6.0	since 3.1.0	since 1.1.0	since 5.8.0	no
v2 migrations	yes	yes	yes, limited to what the driver implements	yes	no
Column strategies (v2)	yes	no	no	yes	no
Transactions for v1 migrations	yes	yes	yes	yes	no
Scope config.json switching database/schema	sets the search_path	switches the database	ignored	sets the search_path	no effect
db:create / db:drop	yes	yes	create does nothing, drop fails (since 1.1.1)	yes	no
Minimum version with the 1.1 fixes	1.6.1	3.1.1	1.1.1	5.8.2

The SQL drivers share the SQL API, the driver pages list their additions and differences. MongoDB has its own NoSQL API.

A scope can also connect to a database of its own, with any driver.

The fixes of the minimum versions above: pg applies the schema setting again, mysql returns a promise from all, supports raw and special default values and no longer hangs on a scope without database, sqlite3 supports db:create and fails clearly without filename or on db:drop, and all of them drop unsupported special default values with a warning instead of failing, together with db-migrate-base 2.4.1.

Older drivers keep working with db-migrate 1.0, db-migrate warns that they run without the migration lock, or without its state management at all.