yogthos/migratus

Migratus running migrations already marked as ran

Open

#206 opened on Nov 8, 2021

View on GitHub
 (5 comments) (0 reactions) (0 assignees)Clojure (99 forks)github user discovery
enhancementhelp wanted

Repository metrics

Stars
 (686 stars)
PR merge metrics
 (PR metrics pending)

Description

I have this row in the schema_migrations table:

20210301103792 2021-09-07 18:00:32.904475 prototype-parirty-changes

and a file called 20210301103792-prototype-parirty-changes.up.sql

yet when I run lein migratus, it still tries to run this migration. How can I make it skip migrations that have already been run (in this case, manually)? What else besides a line in the schema_migrations table does it take and if it looks for some other signal, what is the point of this schema_migrations table?

Contributor guide

Research direction
Examine how migratus matches migration files to database records. Check the file naming convention and ensure the prefix matches exactly, including the separator. Look for any differences in formatting or leading zeros.
Tech stack
None
Domain
database
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Database migrations
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65