Support CLIENT_OPTIONAL_RESULTSET_METADATA #1105
Comments
The flag is not documented here: https://dev.mysql.com/doc/internals/en/capability-flags.html According to the "Low Level Design" part of the worklog, the following is used: #define CLIENT_OPTIONAL_RESULTSET_METADATA (1UL << 25) Further source: https://dev.mysql.com/doc/refman/8.0/en/c-api-optional-metadata.html |
Allow optional resultset metadata. Can potentially improve the performance in many scenario. Issue go-sql-driver#1105
Allow optional resultset metadata. Can potentially improve the performance in many scenario. Issue go-sql-driver#1105
Allow optional resultset metadata. Can potentially improve the performance in many scenario. Issue go-sql-driver#1105
Allow optional resultset metadata. Can potentially improve the performance in many scenario. Issue go-sql-driver#1105
Allow optional resultset metadata. Can potentially improve the performance in many scenario. Issue go-sql-driver#1105
Allow optional resultset metadata. Can potentially improve the performance in many scenario. Issue go-sql-driver#1105
Allow optional resultset metadata. Can potentially improve the performance in many scenario. Issue go-sql-driver#1105
Allow optional resultset metadata. Can potentially improve the performance in many scenario. Issue go-sql-driver#1105
It's right, this option will improve performance in many scenarios with up to 180% QPS performance improvement. Is it possible for |
Issue description
This option will improve performance in many scenarios
https://dev.mysql.com/worklog/task/?id=8134
https://www.facebook.com/weixiang.zhai/posts/678596755543802
The text was updated successfully, but these errors were encountered: