Migration statuses #1914
CarlosLeonCode
started this conversation in
General
Replies: 2 comments 3 replies
-
As I remember, you should run migrations once to auto-create Sequel technical tables. |
Beta Was this translation helpful? Give feedback.
0 replies
-
It seems like you're passing the database URL into the mentioned method for checking migration status instead of a Sequel database object. |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hey guys!
There is some way to check my migrations statuses? as the db:migrate:status command in a Rails app.
I used the below methods:
But none of them works for me.
I got the following error.

And I just have two migrations:


There are inside db/migrations path:

My Rakefile looks like:

And the database structure is:

I don't get it why I got that error when I used one of that commands to check my migration statuses. I suppose that I have to create a task to emulate the db:migrate:status command using one of previous commands.
This is the Repository with the complete code if someone wants to check it out 😃
Beta Was this translation helpful? Give feedback.
All reactions