summaryrefslogtreecommitdiff
path: root/ext/pdo_mysql/php_pdo_mysql_int.h
diff options
context:
space:
mode:
authorNikita Popov <nikita.ppv@gmail.com>2020-12-08 14:28:18 +0100
committerNikita Popov <nikita.ppv@gmail.com>2020-12-08 17:01:56 +0100
commit2df09b9b64ed30c8d999538d1747d511ffd0af9c (patch)
tree79235b368a3d46fae4fec273ec6eba1d1e4d8973 /ext/pdo_mysql/php_pdo_mysql_int.h
parentbfa69d27bc867d62f2b74c189b90e15a0a41e864 (diff)
downloadphp-git-2df09b9b64ed30c8d999538d1747d511ffd0af9c.tar.gz
PDO MySQL: Normalize handling of empty stored procedure result set
MySQL always returns a trailing empty result set for stored procedure calls, which is used to convey status information. The PDO MySQL implementation is presently confused about what to do with it: If mysqlnd is used and native prepared statements are used, this result set is skipped. In all other cases it is not skipped. We also have quite a few XFAILed tests relating to this. This patch normalizes (for PHP-8.0 only) the behavior towards always retaining the empty result set. This is simply how MySQL stored procedures work (some expletives omitted here) and we can't distinguish this "useless" result set from an empty result of a multi query. Multi queries are not a concern for native prepared statements, as PDO does not allow them in that case, but they are a concern for emulated prepared statements. Closes GH-6497.
Diffstat (limited to 'ext/pdo_mysql/php_pdo_mysql_int.h')
0 files changed, 0 insertions, 0 deletions