CLIENT_DEPRECATE_EOF
A capability flag in the MySQL wire protocol. When enabled, it removes the metadata EOF packet and terminates result sets with an OK packet, reducing one round trip. It requires the client and server to interpret packet termination in exactly the same way.
Timeline (last 90 days)
During the MySQL connection handshake, capabilities are negotiated, among which CLIENT_DEPRECATE_EOF changes how the result set ends: the metadata EOF packet disappears and the last packet becomes an OK packet.
MySQL 5.7.5 and above support the CLIENT_DEPRECATE_EOF capability, but the client must actively request the new behavior.
The Node.js driver mysql2 does not request CLIENT_DEPRECATE_EOF, whereas Hyperdrive does.
All Facts (3)
During the MySQL connection handshake, capabilities are negotiated, among which CLIENT_DEPRECATE_EOF changes how the result set ends: the metadata EOF packet disappears and the last packet becomes an OK packet.
50%UnverifiedMySQL 5.7.5 and above support the CLIENT_DEPRECATE_EOF capability, but the client must actively request the new behavior.
50%UnverifiedThe Node.js driver mysql2 does not request CLIENT_DEPRECATE_EOF, whereas Hyperdrive does.
50%