Bug #86875 Inconsistence in docs about what ¨basic datatype' JSON is
| Submitted: | 29 Jun 2017 18:15 | Modified: | 4 Aug 2017 9:06 |
|---|---|---|---|
| Reporter: | Peter Laursen (Basic Quality Contributor) | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: Documentation | Severity: | S3 (Non-critical) |
| Version: | 5.7+ | OS: | Any |
| Assigned to: | CPU Architecture: | Any |
[29 Jun 2017 18:15]
Peter Laursen
[30 Jun 2017 9:27]
MySQL Verification Team
Hello Peter, Thank you for the report! Thanks, Umesh
[4 Aug 2017 9:04]
Jon Stephens
There's nothing inconsistent with the documentation: MySQL has a JSON data type, whose string representation in MySQL uses utf8mb4. Since JSON documents are represented as strings, it appeared to make sense to place the 2 paragraphs dealing with JSON storage requirements in the section covering string type storage requirements, and was not intended to invite question about matters already definitively covered elsewhere. Nevertheless, for the removal of doubt, I've moved these paragraphs into their own JSON Storage Requirements section, which should appear online shortly. Closed in mysqldoc rev 53269.
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.039 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.