Bug #80520 please provide lighter protocol with less metadata
Submitted: 25 Feb 2016 18:56 Modified: 29 Feb 2016 14:50
Reporter: Domas Mituzas Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Server: Connection Handling Severity:S4 (Feature request)
Version:all OS:Any (all)
Assigned to: CPU Architecture:Any

[25 Feb 2016 18:56] Domas Mituzas 
Description:
current mysql protocol responses return field names, column aliases, table names, field types and even catalog "def". All that fat data transfer makes network traffic bloated, clients more expensive, etc. Most of database clients may already know what they are reading anyway. 

Prepared statements are not helping here, as they don't support dynamic nature of various applications - on systems with thousands of systems current prepared statement framework falls short early. 

Making protocol cheaper (guided by client flag) would be an easy step towards great future, etc.

How to repeat:
check out traffic of high-throughput OLTP systems that do lots of queries. oh no, thats ugly!

Suggested fix:
have zero-metadata protocol option
[29 Feb 2016 14:50] MySQL Verification Team 
Having a lighter protocol could make sense if that is optional, just as you described.

Verified feature request.