content_image/753493.jpg
### @3=NULL ### SET ### @1=1 ### @2=’pear’ ### @3=’2009:01:01’ ... # at 400 #080828 15:03:08 server id 1 end_log_pos 442 Delete_rows: table id 17 flags: STMT_END_F ### DELETE FROM test.t ### WHERE ### @1=1 ### @2=’pear’ ### @3=’2009:01:01’ 

<img src='content_image/753493.jpg'>

## Note 

You should not suppress BINLOG  statements if you intend to re-execute mysqlbinlog  output. 

The SQL statements produced by --verbose  for row events are much more readable than the corresponding BINLOG  statements. However, they do not correspond exactly to the original SQL statements that generated the events. The following limitations apply: 

•The original column names are lost and replaced by @ N , where N  is a column number. 

•Character set information is not available in the binary log, which affects string column display: 

•There is no distinction made between corresponding binary and nonbinary string types ( BINARY  and CHAR , VARBINARY  and VARCHAR , BLOB  and TEXT ). The output uses a data type of STRING  for fixed- length strings and VARSTRING  for variable-length strings. 

•For multibyte character sets, the maximum number of bytes per character is not present in the binary log, so the length for string types is displayed in bytes rather than in characters. For example, STRING(4)  is used as the data type for values from either of these column types: 

CHAR(4) CHARACTER SET latin1 CHAR(2) CHARACTER SET ucs2 

•Due to the storage format for events of type UPDATE_ROWS_EVENT , UPDATE  statements are displayed with the WHERE  clause preceding the SET  clause. 

Proper interpretation of row events requires the information from the format description event at the beginning of the binary log. Because mysqlbinlog  does not know in advance whether the rest of the log contains row events, by default it displays the format description event using a BINLOG  statement in the initial part of the output. 

If the binary log is known not to contain any events requiring a BINLOG  statement (that is, no row events), the --base64-output=NEVER  option can be used to prevent this header from being written. 

## 4.6.9.3 Using mysqlbinlog to Back Up Binary Log Files 

By default, mysqlbinlog  reads binary log files and displays their contents in text format. This enables you to examine events within the files more easily and to re-execute them (for example, by using the output as input to mysql ). mysqlbinlog  can read log files directly from the local file system, or, with the --read- from-remote-server  option, it can connect to a server and request binary log contents from that server. mysqlbinlog  writes text output to its standard output, or to the file named as the value of the --result- file= file_name  option if that option is given. 

•mysqlbinlog Backup Capabilities 

