Fix extract_signature when sql is a bytes object #366
Closed
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.
In psycopg2's
execute_batch
andexecute_values
functions, the SQL statement is a bytes object and not a string (see psycopg2's extras.py#L1198). This may also be a problem for other database adapters but I'm only aware of this behavior with psycopg2.extract_signature
raises a TypeError when thesql
parameter is a bytes object becausesql.find(" ")
expects a bytes object and" "
is a string.My proposed solution is to check whether
sql
is a bytes object and decode if necessary.I have signed the CLA.