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

SQL: Fix locking with MS SQL Server #3394

Merged
merged 4 commits into from
Sep 20, 2024
Merged

SQL: Fix locking with MS SQL Server #3394

merged 4 commits into from
Sep 20, 2024

Conversation

reinkrul
Copy link
Member

Fixes #3393

@reinkrul reinkrul requested review from woutslakhorst and gerardsn and removed request for woutslakhorst September 19, 2024 15:24
@reinkrul reinkrul marked this pull request as ready for review September 19, 2024 15:24
Copy link
Member

@woutslakhorst woutslakhorst left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's no coverage on the status list MSSql logic. Could you extend the oauth/statuslist e2e tests with mssql?

discovery/store.go Outdated Show resolved Hide resolved
@reinkrul
Copy link
Member Author

There's no coverage on the status list MSSql logic. Could you extend the oauth/statuslist e2e tests with mssql?

I did that in the RFC021 e2e-test as part of #3391 by enabling revocation status for the issued credentials. Although I don't necessarily think that's the right test (because it was originally intended to be RFC021-specific), having a varying set of databases tested in different tests here and there, is not very maintainable. As RFC021 is actually the "only" use case/flow we truly support and use for v6, maybe we can keep all variants we need (MySql/Postgres/MSSQL Server) there?

@reinkrul reinkrul merged commit 875a386 into master Sep 20, 2024
7 of 9 checks passed
@reinkrul reinkrul deleted the mssql-locking-support branch September 20, 2024 09:07
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.

Storage: MS SQL Server does not properly support SELECT FOR UPDATE
2 participants