The command code 254 (former COM_MULTI) is now reserved,
The corresponding capability flag in the protocol is reserved as well.
Do not reuse them just yet.
Verify that Connector/C mariadb_stmt_execute_direct functionality
does *not* depend on COM_MULTI in protocol.
Reading C/C code suggest that it would, but this appears to be confusion
because of unfortunate naming.
Actually, Connector/C does sort-of pipelining under the cover,
accumulating data from several commands (COM_PREPARE, COM_STMT_EXECUTE)
and sending them to server, all at once.
commit 105b879d0f541f049a131a5c3b99d678fc7d3213 introduced this
warning. The warning looks harmless, but GCC does not understand
that the initialization and the use of the variables are guarded
by the same predicate.
The test was broken in commit f40ca33bbc605af28492b58dde35bf2a97126b5f.
The background DROP TABLE queue in InnoDB will continue to
use names like #sql-ib, and we must filter out those file names.
When commit 562c037b485b25f76fc7cb8e2c526d532450df7a
removed FIL_TYPE_LOG, the function fil_type_is_data()
became redundant, that is, always returning true for
a valid value of fil_space_t::purpose. Remove it.
Ship mariadb.service and mysql[d].service symlinks
Create symlinks during configure time and install them. This is
necessary as Alias support from systemd service file was dropped with:
6af0bd69074725c8d8b10f07ed4ccc013d010322