Make use_list param configurable in Connector #166
Labels
feature
A new functionality
Comments
Merged
artembo
added a commit
that referenced
this issue
Oct 18, 2020
It is set up to be converted to lists by default. Django expects row type to be tuple. Also tuples tend to perform better than lists and it is good if it can be configurable. Closes #166
artembo
added a commit
that referenced
this issue
Oct 26, 2020
It is set up to be converted to lists by default. Django expects row type to be tuple. Also tuples tend to perform better than lists and it is good if it can be configurable. Closes #166
artembo
added a commit
that referenced
this issue
Oct 28, 2020
It is set up to be converted to lists by default. Django expects row type to be tuple. Also tuples tend to perform better than lists and it is good if it can be configurable. Closes #166
artembo
added a commit
that referenced
this issue
Oct 30, 2020
It is set up to be converted to lists by default. Django expects row type to be tuple. Also tuples tend to perform better than lists and it is good if it can be configurable. Closes #166
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
By default
use_listparameter tells msgpack to unpack array toPython's list which is not hashable and can not be used as a dict keys
and sets elements. Django expects the response rows to be tuples
because it will be used in python set() [1]
Need to make it configurable to let the user choose which type of rows
can be fetched from the database response.
[1] https://github.com/django/django/blob/stable/3.0.x/django/contrib/auth/management/__init__.py#L72
The text was updated successfully, but these errors were encountered: