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

Fix #1592: Implement procedure sp_getapplock for locking activations on MSSQL (backport) #1617

Closed
wants to merge 1 commit into from

Conversation

banterCZ
Copy link
Member

(cherry picked from commit cafed8c)

@banterCZ
Copy link
Member Author

This is quite risky, see #1620 for a quick fix.

Copy link
Member

@romanstrobl romanstrobl left a comment

Choose a reason for hiding this comment

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

This fix is risky because of the high number of changes. I will approve it so it can be used, however the fix should be tested thoroughly before putting into a release.

@banterCZ banterCZ changed the title Fix #1592: Implement procedure sp_getapplock for locking activations on MSSQL (#1593) Fix #1592: Implement procedure sp_getapplock for locking activations on MSSQL (backport) Jul 26, 2024
@banterCZ
Copy link
Member Author

Not needed anymore, introduced in 1.8.x

@banterCZ banterCZ closed this Jul 29, 2024
@banterCZ banterCZ deleted the issues/1592-mssql-locking branch July 29, 2024 12:55
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.

2 participants