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

Enable gaplock protection when using trilogy mysql adapter #528

Conversation

jurre
Copy link
Contributor

@jurre jurre commented Dec 21, 2023

In #522 the ability to enable gaplock protection manually was removed, likely assuming there was no need for this since it's enabled by default when using an adapter that is named mysql*, however we use
https://github.com/trilogy-libraries/trilogy which has been gaining some traction in the community and this change now leaves us without a way to enable the functionality.

I think it makes most sense to enable the functionality by default when using this new adapter as well, and keep config requirements minimal, so I added a little check for that adapter name as well.

In gocardless#522 the ability to
enable gaplock protection manually was removed, likely assuming there
was no need for this since it's enabled by default when using an adapter
that is named `mysql*`, however we use
https://github.com/trilogy-libraries/trilogy which has been gaining some
traction in the community and this change now leaves us without a way to
enable the functionality.

I think it makes most sense to enable the functionality by default when
using this new adapter as well, and keep config requirements minimal, so
I added a little check for that adapter name as well.
@stephenbinns stephenbinns merged commit bea0a4b into gocardless:master Jan 5, 2024
78 checks passed
@jurre jurre deleted the jurre/enable-gaplock-protection-on-trilogy-adapter branch February 5, 2024 14:51
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.

None yet

2 participants