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

Misleading wasRolledBack method #662

Closed
graineri opened this issue Dec 7, 2017 · 2 comments
Closed

Misleading wasRolledBack method #662

graineri opened this issue Dec 7, 2017 · 2 comments
Labels
type: feature A new feature

Comments

@graineri
Copy link

graineri commented Dec 7, 2017

This only applies to Lettuce 5.x.

Taking a look at TransactionResult interface I noticed there is a wasRolledBack method which I find somewhat misleading since there is no such thing in Redis.

I finally realized the intent of this method once I read TransactionCommandTest: it actually means that the transaction was discarded (this behavior is explained here).

@mp911de
Copy link
Collaborator

mp911de commented Dec 7, 2017 via email

@mp911de mp911de added this to the Lettuce 5.1.0 milestone Dec 19, 2017
@mp911de mp911de added the type: feature A new feature label Dec 19, 2017
mp911de added a commit that referenced this issue Dec 19, 2017
Add wasDiscarded() method to resolve naming ambiguities with wasRolledBack(). Redis has no notion of transaction rollbacks, Redis is only able to conditionally execute a transaction batch.
@mp911de
Copy link
Collaborator

mp911de commented Dec 19, 2017

That's fixed now.

@mp911de mp911de closed this as completed Dec 19, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: feature A new feature
Projects
None yet
Development

No branches or pull requests

2 participants