Skip to content

Wrong SQL result processing #146

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

Conversation

nicktorwald
Copy link

Fix a regression related to processing of SQL response.
Fix a wrong parsing of SQL tuple result.

Fixes: #141

Fix a regression related to processing of SQL response.
Fix a wrong parsing of SQL tuple result.

Fixes: #141
@nicktorwald nicktorwald requested a review from Totktonada March 29, 2019 18:04
@coveralls
Copy link

Coverage Status

Coverage increased (+1.0%) to 64.156% when pulling 24a99a7 on nicktorwald/gh-141-wrong-response-code-comparison into 4715727 on master.

@Totktonada
Copy link
Member

I expanded a bit the commit message and pushed it in 9e3245d.

@Totktonada Totktonada closed this Mar 30, 2019
@Totktonada Totktonada deleted the nicktorwald/gh-141-wrong-response-code-comparison branch March 30, 2019 05:50
@Totktonada
Copy link
Member

Also filed #148

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.

3 participants