Skip to content
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

client: Fix sql migration step for oidc #919

Merged
merged 5 commits into from
Jul 11, 2018
Merged

client: Fix sql migration step for oidc #919

merged 5 commits into from
Jul 11, 2018

Conversation

aeneasr
Copy link
Member

@aeneasr aeneasr commented Jul 11, 2018

A bug was introduced in beta.5 which caused the SQL migrations to fail if data existed in the database already. This patch resolves that and adds test cases for the migration steps by adding data after each migration.

Closes #918

A bug was introduced in beta.5 which caused the SQL migrations to fail if data existed in the database already. This patch resolves that and adds test cases for the migration steps by adding data after each migration.

Closes #918

Signed-off-by: arekkas <[email protected]>
arekkas added 4 commits July 11, 2018 15:38
A bug was introduced in beta.5 which caused the SQL migrations to fail if data existed in the database already. This patch resolves that and adds test cases for the migration steps by adding data after each migration.

Closes #918

Signed-off-by: arekkas <[email protected]>
A bug was introduced in beta.5 which caused the SQL migrations to fail if data existed in the database already. This patch resolves that and adds test cases for the migration steps by adding data after each migration.

Closes #918

Signed-off-by: arekkas <[email protected]>
A bug was introduced in beta.5 which caused the SQL migrations to fail if data existed in the database already. This patch resolves that and adds test cases for the migration steps by adding data after each migration.

Closes #918

Signed-off-by: arekkas <[email protected]>
A bug was introduced in beta.5 which caused the SQL migrations to fail if data existed in the database already. This patch resolves that and adds test cases for the migration steps by adding data after each migration.

Closes #918

Signed-off-by: arekkas <[email protected]>
@aeneasr aeneasr merged commit ad5e8bc into master Jul 11, 2018
@aeneasr aeneasr deleted the fix-default branch July 11, 2018 14:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

migration 0.9.x -> 1.0: sector_identifier_uri contains null values
1 participant