| Bug #77788 | Document how Connector uses COM_STMT_SEND_LONG_DATA | ||
|---|---|---|---|
| Submitted: | 21 Jul 2015 6:10 | Modified: | 19 Feb 2016 18:19 |
| Reporter: | Andrii Nikitin | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | Connector / Python Documentation | Severity: | S3 (Non-critical) |
| Version: | 2.0.4 | OS: | Any |
| Assigned to: | Paul DuBois | CPU Architecture: | Any |
[19 Feb 2016 18:19]
Paul DuBois
Thank you for your bug report. This issue has been addressed in the documentation. The updated documentation will appear on our website shortly. Added info to this section: http://dev.mysql.com/doc/connector-python/en/connector-python-api-mysqlcursorprepared.html

Description: MySQL protocol has option to send prepared parameters via dedicated command COM_STMT_SEND_LONG_DATA Connector/Python uses it when parameter is IOBase interface - please document it How to repeat: Following code shows COM_STMT_SEND_LONG_DATA in general log as "Long Data": cur = cnx.cursor(prepared=True) cur.execute("SELECT (%s)", (io.BytesIO(bytes("A", "latin1")), )) Suggested fix: na