You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Although Table_map events include some column metadata information,
such as type and length, it lacks the necessary information to fully
deduce column's definition and to interpret its values. For example,
it lacks information such as the column name, whether an integer type
is signed or unsigned, or the character set of string types. This
makes it rather difficult for external programs to extract meaningful
row data from row-based events.
In order to enable external programs to fully deduce the table/column
definitions, a new Table_metadata event is added. The purpose of this
event is to describe the structure and other properties of the table
and its columns, such as name, SQL type name, character set, etc. Each
Table_metadata event follows a Table_map. Whether Table_metadata
events are written to the binary log can be controlled using the
system variable binlog_rows_table_metadata_events.
0 commit comments