Add support for explicit table-level locks #205
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Photonios
force-pushed
the
explicit-table-locking
branch
from
41b7423 to
ecc1bf5
Compare
Photonios
force-pushed
the
explicit-table-locking
branch
from
ecc1bf5 to
63d8608
Compare
sewi-cpan
reviewed
Apr 5, 2023
| lock_signature = ( | ||
| "public", | ||
| mocked_model._meta.db_table, | ||
| "AccessExclusiveLock", |
Contributor
There was a problem hiding this comment.
What about using @pytest.mark.parametrize with PostgresTableLockMode to ensure that all lock modes are working?
sewi-cpan
approved these changes
Apr 6, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.