Add support for Decimal parsing in protocol.py #18
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.
Currently a Decimal when queried from MySQLCursorPrepared is returned as a bytearray. The api states that the values FieldType.DECIMAL, FieldType.NEWDECIMAL are just a char array which I guess is why it's parsed by the string parser already.
I haven't tested the encoding on py2 but wanted feedback on whether this is a fix that would be included. I can add support/test if this seems reasonable.
It seem appropriate to convert these to Decimal here because the code notes that this should be done.