Question 1

How do I rollback a migration in Drift?

Accepted Answer

Use the Leiningen command `lein migrate -version <number>` to migrate to a specific version, which automatically runs down functions for versions higher than the target. For a full rollback, pass version 0.

Question 2

Drift vs Migratus: which is better for Clojure?

Accepted Answer

Drift is simpler and Rails-inspired, ideal for teams familiar with that workflow, while Migratus offers more features like built-in version tracking and multiple database support. Choose Drift for minimalism or Migratus for richer functionality.

Question 3

How to handle multiple databases with Drift?

Accepted Answer

Implement custom version tracking functions in migrate-config.clj that manage separate version tables for each database, and use initialization hooks to switch connections, as Drift doesn't provide built-in multi-database support.

Question 4

Can Drift be used without Leiningen?

Accepted Answer

Yes, but it's cumbersome; you can call Drift directly from Java or Clojure code using its API, but you'll lose the convenience of Leiningen commands and need to handle migration runs programmatically.

Question 5

How to seed data with Drift migrations?

Accepted Answer

Create a migration file with up/down functions that include data insertion or deletion logic using your preferred database library, but note that Drift doesn't have special seeding features, so manage it manually.

Question 6

What happens if a migration fails in Drift?

Accepted Answer

Drift doesn't provide automatic rollback on failure; you must handle errors manually in your up/down functions, potentially leaving the database in an inconsistent state if not implemented carefully.

Drift

What is Drift?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions