Bug #115360 Contribution: Classic Protocol: Decoding MYSQL_TYPE_JSON in binary resultse ...
| Submitted: | 17 Jun 2024 14:31 | Modified: | 30 Aug 2024 16:27 |
|---|---|---|---|
| Reporter: | OCA Admin (OCA) | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: Documentation | Severity: | S3 (Non-critical) |
| Version: | 8.4.0 | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | Contribution | ||
[17 Jun 2024 14:31]
OCA Admin
[17 Jun 2024 14:31]
OCA Admin
Contribution submitted via Github - Classic Protocol: Decoding MYSQL_TYPE_JSON in binary resultset (*) Contribution by Daniël van Eeden (Github dveeden, mysql-server/pull/550#issuecomment-2169254075): I confirm the code being submitted is offered under the terms of the OCA, and that I am authorized to contribute it.
Contribution: git_patch_1921871091.txt (text/plain), 1.75 KiB.
[17 Jun 2024 14:56]
MySQL Verification Team
Hello Daniël, Thank you for the report and contribution. regards, Umesh
[30 Aug 2024 16:27]
Jon Stephens
Documented fix as follows in the MySQL 8.4.3 and 9.1.0 changelogs:
MYSQL_TYPE_JSON was missing from the description of binary
resultsets in the MySQL source code documentation.
Our thanks to Daniël van Eeden for the contribution.
Closed.
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.052 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.