Replies: 6 comments
|
Would also love a way to disable this. Resorted to patch the package to remove the line for now |
0 replies
|
Would be great to disable this rather than having to patch the package. |
0 replies
|
+1 Would also love a way to disable this. This causes issues when trying to migrate during deploys to render.com since the user registered with the DB does not have permission to create schemas. |
0 replies
|
+1 also working with DB that has no permission to create schema |
0 replies
|
+1 to have a way to disable this with config. Our db creds don't have permission to create schema and we also create it manually before deploying new schema first time |
0 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.
My database user don't have permissions to create an schema, and this is breaking the migrations on the first step
CREATE SCHEMA IF NOT EXISTS "public". There is any way to disable this step?It's a postgres database
(even after manually creating the tables, and inserting the migrations in the migrations table it's still breaking because it's tries to create the schema)
All reactions