The Ultimate Guide to High Availability with MariaDB

TABLE_MAP_EVENT

You are viewing an old version of this article. View the current version here.

Used for row-based binary logging beginning (binlog_format=ROW in my.cnf)

This event precedes each row operation event and maps a table definition to a number, where the table definition consists of database and table names.

  • Event Type is 19 (0x13)

Fields

Fixed data part:

Variable data part:

  • uint<1> Database name length.
  • string<EOF> The database name (null-terminated).
  • uint<1> Table name length.
  • string<EOF> The table name (null-terminated).
  • int<lenenc> The number of columns in the table.
  • byte<n> An array of 'n' column types, one byte per column.
  • int<lenenc> The length of the metadata block.
  • byte<n> The metadata block;
  • byte<n> Bit-field indicating whether each column can be NULL, one bit per column.

Example From mysqlbinlog

# at 847
#171206 13:43:00 server id 10124  end_log_pos 892 CRC32 0xbe3c6b05 	Table_map: `test`.`t4` mapped to number 33
# at 892

Complete Event

d4 e5 27 5a 13 8c 27 00  00 2d 00 00 00 7c 03 00  ..'Z..'..-...|..
00 00 00 21 00 00 00 00  00 01 00 04 74 65 73 74  ...!........test
00 02 74 34 00 01 03 01  01 05 6b 3c be           ..t4......k<.

Comments

Comments loading...
Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.