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

sql: Unable to run migrations when coming from beta.9 #1185

Closed
aeneasr opened this Issue Nov 21, 2018 · 4 comments

Comments

Projects
None yet
2 participants
@aeneasr
Member

aeneasr commented Nov 21, 2018

No description provided.

@aeneasr aeneasr added this to the v1.0.0-rc.2 milestone Nov 21, 2018

@aeneasr

This comment has been minimized.

Member

aeneasr commented Nov 21, 2018

Fix: ory/x#17

aeneasr added a commit that referenced this issue Nov 21, 2018

sql: Resolve beta.9 -> rc.1 migration issue
Closes #1185

Signed-off-by: aeneasr <aeneas@ory.sh>

aeneasr added a commit that referenced this issue Nov 21, 2018

sql: Resolve beta.9 -> rc.1 migration issue
Closes #1185

Signed-off-by: aeneasr <aeneas@ory.sh>

aeneasr added a commit that referenced this issue Nov 21, 2018

sql: Resolve beta.9 -> rc.1 migration issue
Closes #1185

Signed-off-by: aeneasr <aeneas@ory.sh>

aeneasr added a commit that referenced this issue Nov 21, 2018

sql: Resolve beta.9 -> rc.1 migration issue (#1186)
Closes #1185

Signed-off-by: aeneasr <aeneas@ory.sh>
@eudavidf

This comment has been minimized.

eudavidf commented Nov 22, 2018

Running rc2 miggrate database we received this:

Applying jwk SQL migrations...
Applied 1 jwk SQL migrations.
Applying client SQL migrations...
Applied 3 client SQL migrations.
Applying consent SQL migrations...
An error occurred while running the migrations: could not apply consent SQL migrations: Could not migrate sql schema, applied 3 migrations: pq: se ha denegado el permiso para cambiar la opción «session_replication_role» handling 7

(Last part translated: permission denied to change option "session_replication_role")

@aeneasr

This comment has been minimized.

Member

aeneasr commented Nov 22, 2018

@eudavidf

This comment has been minimized.

eudavidf commented Nov 22, 2018

Thanks!
We 've solved it making hydra db user SUPERUSER.
After migrating, we've removed the permission.
Does it worth reflect this circumstance in the docs?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment