Skip to content

DATAREDIS-226 - Syntax exceptions using lettuce should be reported immediately. #66

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

Closed
wants to merge 2 commits into from

Conversation

christophstrobl
Copy link
Member

If running in transaction mode we now do a rudimentary check if the provided number of arguments matches the ones defined for RedisCommand to execute.

If the Command passes this first check and causes an error on redis server one has to check results for Command.getOutput().hasError().

christophstrobl added a commit that referenced this pull request Apr 28, 2014
…mediately.

If running in transaction mode we now do a rudimentary check if the provided number of arguments matches the ones defined for RedisCommand to execute. 

If the Command passes this first check and causes an error on redis server one has to check results for Command.getOutput().hasError().

Original Pull Request: #66
…mediately.

If running in transaction mode we now do a rudimentary check if the provided number of arguments matches the ones defined for the RedisCommand to execute. 

If the command passes this first check and causes an error on redis server one has to check results for Command.getOutput().hasError().

Original Pull Request: #66.
christophstrobl added a commit that referenced this pull request Apr 29, 2014
…mediately.

If running in transaction mode we now do a rudimentary check if the provided number of arguments matches the ones defined for the RedisCommand to execute.

If the command passes this first check and causes an error on redis server one has to check results for Command.getOutput().hasError().

Original Pull Request: #66.
@thomasdarimont
Copy link

Merged into master via: ce8d932.

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