Bsb/issue 377 - calls of JSONOperations run outside of watch, multi, exec transaction #653
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
JSON operations now automatically detect and participate in Redis transactions when executed within a SessionCallback/transaction context. This ensures proper atomicity when combining JSON operations with other Redis commands in transactions. - Added transaction detection using RedisConnection.isQueueing() - JSON.SET commands are properly queued using connection.execute() - Maintains backward compatibility with existing non-transactional usage - Added comprehensive test coverage for transaction scenarios Fixes redis#377
bsbodden
force-pushed
the
bsb/issue-377
branch
from
a1f9729 to
6c590f2
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
See #377