You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@shardingsphere.apache.org by GitBox <gi...@apache.org> on 2020/02/18 10:48:08 UTC
[GitHub] [incubator-shardingsphere] tuohai666 opened a new issue #4355:
Different ComStmtPrepare process between MySQL Connector/J and MySQL C API
tuohai666 opened a new issue #4355: Different ComStmtPrepare process between MySQL Connector/J and MySQL C API
URL: https://github.com/apache/incubator-shardingsphere/issues/4355
Column type of char in response of ComStmtPrepare handled differently between MySQL Connector/J and MySQL C API.
Connector/J accepts MYSQL_TYPE_VARCHAR, MYSQL_TYPE_VAR_STRING and MYSQL_TYPE_STRING.
While C API checks strictly and only accept MYSQL_TYPE_VAR_STRING and MYSQL_TYPE_STRING, because column type will be stored in struct MYSQL_STMT (fields.type) but MYSQL_TYPE_VARCHAR is not allowed to bind result.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [incubator-shardingsphere] tuohai666 closed issue #4355: Different
ComStmtPrepare process between MySQL Connector/J and MySQL C API
Posted by GitBox <gi...@apache.org>.
tuohai666 closed issue #4355: Different ComStmtPrepare process between MySQL Connector/J and MySQL C API
URL: https://github.com/apache/incubator-shardingsphere/issues/4355
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services