Bug #88212 OK Packet docs incorrectly label info field as EOF string

• Submitted: 24 Oct 2017 23:36
• Modified: 25 Oct 2017 5:41
• Reporter: Aaron Balsara
• Status: Verified
• Category: MySQL Server: Documentation
• Severity: S3 (Non-critical)
• Version: 8.0, 5.7
• OS: Any
• CPU Architecture: Any

[24 Oct 2017 23:36] Aaron Balsara

Description:
The MySQL documentation on the OK packet (https://dev.mysql.com/doc/dev/mysql-server/8.0.0/page_protocol_basic_ok_packet.html) states that if CLIENT_SESSION_TRACK is not send, then the info field is sent as a STRING<EOF>.

This is not correct as the string is sent as a length encoded string. This can be seen in the protocol file which writes the info (https://github.com/mysql/mysql-server/blob/8.0/sql/protocol_classic.cc#L709) and the client code which reads the same field (https://github.com/mysql/mysql-server/blob/8.0/sql-common/client.cc#L1048-L1049)

How to repeat:
Read docs, read code, they don't match up

Suggested fix:
change string<EOF> to string<lenenc> for the info field in the OK Packet

[25 Oct 2017 5:41] MySQL Verification Team

Hello Aaron,

Thank you for the report and feedback.

Thanks,
Umesh