Closed little-dude closed 5 years ago
Hi,
The migrations are run based in order of the timestamps, but it looks like the db might've gotten into a bad state. Migratus creates a table called schema_migrations
that tracks the migrations that have already been applied. The ones in the table will be skipped when migrations are run. One thing to try would be to run (user/reset-db)
from the REPL.
@yogthos thank you, I dropped schema_migrations
and the custom datatype and it all works now!
👍
Hi,
In Luminus I created these three migrations:
message-status
references the tables created by the two other migrations:When running
(migrate)
, I get:I'm confused because I don't understand:
message-status
migration? I assumed it would run the migrations based on their timestamps since the README says:Sorry if this is a dumb question, I'm still working my way through Web Development with Clojure, Third Edition so I'm pretty new to this.