Bug #99416 router mock server protocol types are inconsistent with mysql server types
Submitted: 2 May 2020 3:23 Modified: 8 May 2020 21:00
Reporter: Daniel Black Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Router Severity:S3 (Non-critical)
Version:8.0.18 OS:Any
Assigned to: CPU Architecture:Any

[2 May 2020 3:23] Daniel Black 
Description:
https://github.com/mysql/mysql-server/blob/8.0/router/src/mock_server/src/mysql_protocol_c...

  NEWDECIMAL = 0xf7,
  ENUM = 0xf7,

Both can't be right.

From https://github.com/mysql/mysql-server/blob/8.0/include/field_types.h#L79

NEWDECIMAL = 246 (0xf6)

Missing in mock server

MYSQL_TYPE_JSON and MYSQL_TYPE_TIMESTAMP2

How to repeat:
Look at the code.

Suggested fix:
Correct mock server types based on real server types.
[4 May 2020 4:15] MySQL Verification Team 
Hello Daniel,

Thank you for the report and feedback.

regards,
Umesh
[8 May 2020 21:00] Philip Olson 
Posted by developer:
 
Fixed as of the upcoming MySQL Router 8.0.21 release, and here's the proposed changelog entry from the documentation team:

Updated mock_server MySQL Server type definitions; fixed NEWDECIMAL and
added TIMESTAMP2 and JSON.

Thank you for the detailed bug report.