-
Notifications
You must be signed in to change notification settings - Fork 85
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migrations table with postgres schema #80
Comments
Has there been any solution found? I guess I've just stumbled upon the similar issue using Joplin. But the error message (for
|
PRs to fix this are welcome. I haven't had the chance to investigate this myself. |
I'm also seeing the issue. Appears to happen (at least for me) when specifying a schema (other than defaulting to 'public'). |
I had a similar issue that was caused b/c ragtime was trying to create the table in a schema that did not yet exist. I fixed it by first creating the schema I wanted the migrations table to be in, then ragtime was able to create the migrations table in my schema. |
Hello,
I tried to change the migrations table to one using a postgres schema:
And I get:
If I change, for example to
directory_ragtime_migrations
, everything works as expected.The text was updated successfully, but these errors were encountered: