Open donbonifacio opened 9 years ago
Has there been any solution found? I guess I've just stumbled upon the similar issue using Joplin. But the error message (for :migrations-table "myschema.migrations"
) looks like this:
PSQLException ERROR: relation "migrations" already exists org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse (QueryExecutorImpl.java:2455)
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.