Capability matrix

Every engine DBLift ships with, what to install for it, and the three behaviours that change how you write a migration: whether DDL rolls back, how indexes are built, and whether SQL migrations apply at all.

Engines

The type value goes under database: in dblift.yaml. The driver is installed by the extra beside it; you never import it yourself.

EnginetypeInstallDriver

PostgreSQLpostgresqlpip install "dblift[postgresql]"psycopgMySQLmysqlpip install "dblift[mysql]"pymysqlMariaDBmariadbpip install "dblift[mariadb]"pymysqlOracleoraclepip install "dblift[oracle]"python-oracledbSQL Serversqlserverpip install "dblift[sqlserver]"pymssqlIBM Db2db2pip install "dblift[db2]"ibm_db_saSQLitesqlitepip install "dblift"sqlite3DuckDBduckdbpip install "dblift[duckdb]"duckdbSnowflakesnowflakepip install "dblift[snowflake]"snowflake-connector-pythonAmazon Redshiftredshiftpip install "dblift[redshift]"redshift_connectorAzure Cosmos DBcosmosdbpip install "dblift[cosmosdb]"azure-cosmosMongoDBmongodbpip install "dblift[mongodb]"pymongoAurora PostgreSQLaurora-postgresqlpip install "dblift[aurora-postgresql]"psycopgGoogle AlloyDBalloydbpip install "dblift[alloydb]"psycopgNeonneonpip install "dblift[neon]"psycopgSupabasesupabasepip install "dblift[supabase]"psycopgTimescaleDBtimescaledbpip install "dblift[timescaledb]"psycopgCituscituspip install "dblift[citus]"psycopgCockroachDBcockroachdbpip install "dblift[cockroachdb]"psycopgYugabyteDByugabytedbpip install "dblift[yugabytedb]"psycopg

PostgreSQL-wire engines. Aurora PostgreSQL, AlloyDB, Neon, Supabase, TimescaleDB, Citus and YugabyteDB speak the PostgreSQL wire protocol. Keep your postgresql:// connection string and set the type to the engine — DBLift uses the PostgreSQL behaviour for everything except the differences listed below.

Does a failed migration roll back?

This is the single biggest difference between engines. Where DDL is transactional, a migration that fails half-way leaves the schema untouched. Where DDL auto-commits, the statements that already ran stay applied and you finish the cleanup yourself — write an undo script for those migrations.

Azure Cosmos DB has no transactions of any kind.

Building an index without blocking

Azure Cosmos DB is not SQL

Cosmos DB and MongoDB are the document engines. Neither accepts SQL migrations, and neither has transactions or transactional DDL, so nothing rolls back. Migrations are Python, written against the vendor SDK. Everything else on this page — versioning, history, the schema history table — works the same way.