We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Since the connection has been reserved for this purpose only and the Exec documentation even states that it puts the connection back to normal.
Requiring Close feels pretty cumbersome to me.
Please deprecate use of Transaction.Close and make it a no-op after Exec/Discard.
Transaction.Close
Normal and expected flow for transactions would be:
t, _ := redis.Transaction() _ = transaction.Watch("mykey") // work and queue up commands if someError { _ = t.Discard() } else { _ = t.Exec() }
The text was updated successfully, but these errors were encountered:
A pull request will be appreciate.
Sorry, something went wrong.
No branches or pull requests
Since the connection has been reserved for this purpose only and the Exec documentation even states that it puts the connection back to normal.
Requiring Close feels pretty cumbersome to me.
Please deprecate use of
Transaction.Close
and make it a no-op after Exec/Discard.Normal and expected flow for transactions would be:
The text was updated successfully, but these errors were encountered: