Bug #71124 | callproc function with bytes parameters | ||
---|---|---|---|
Submitted: | 10 Dec 2013 15:18 | Modified: | 12 Mar 2014 1:33 |
Reporter: | Bulat Gaifullin | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | Connector / Python | Severity: | S1 (Critical) |
Version: | 1.0.12-1 | OS: | Linux (Fedora19) |
Assigned to: | CPU Architecture: | Any | |
Tags: | bytes, connector, python |
[10 Dec 2013 15:18]
Bulat Gaifullin
[17 Dec 2013 12:16]
Geert Vanderkelen
Posted by developer: Problem: executing call procedures and getting the result is done by using session variables. These session variables are typeless. Thus, a VARBINARY, we can not handle it correctly and check if it is 'binary' or not.
[17 Dec 2013 12:23]
Geert Vanderkelen
Posted by developer: A not-so-good workaround, but might help when really needed, is to use "use_unicode=False" for connection dealing with VARBINARY and calling stored procedures.
[17 Dec 2013 17:23]
Bulat Gaifullin
It is possible to extract types of variables that will be passed to callproc method and use this knowledge to convert SQL-result back to python variables properly in fetchone method.
[24 Feb 2014 13:00]
Bulat Gaifullin
any updates?
[12 Mar 2014 1:33]
Paul DuBois
Noted in 1.2.1 changelog. Connector/Python now permits the type for stored procedure parameters to be specified. To do this, specify a parameter as a two-item tuple consisting of the parameter value and type. For more information, see http://dev.mysql.com/doc/connector-python/en/connector-python-api-mysqlcursor-callproc.htm...