MySQL  8.0.21
Source Code Documentation
load_data_events.h File Reference

LOAD DATA INFILE is not written to the binary log like other statements. More...

#include <sys/types.h>
#include "statement_events.h"
#include "table_id.h"

Go to the source code of this file.

Classes

class  binary_log::Execute_load_query_event
 Event responsible for LOAD DATA execution, it similar to Query_event but before executing the query it substitutes original filename in LOAD DATA query with name of temporary file. More...
 
class  binary_log::Delete_file_event
 DELETE_FILE_EVENT occurs when the LOAD DATA failed on the master. More...
 
class  binary_log::Append_block_event
 This event is created to contain the file data. More...
 
class  binary_log::Begin_load_query_event
 Event for the first block of file to be loaded, its only difference from Append_block event is that this event creates or truncates existing file before writing data. More...
 

Namespaces

 binary_log
 The namespace contains classes representing events that can occur in a replication stream.
 

Macros

#define DUMPFILE_FLAG   0x1
 
#define OPT_ENCLOSED_FLAG   0x2
 
#define REPLACE_FLAG   0x4
 
#define IGNORE_FLAG   0x8
 
#define FIELD_TERM_EMPTY   0x1
 
#define ENCLOSED_EMPTY   0x2
 
#define LINE_TERM_EMPTY   0x4
 
#define LINE_START_EMPTY   0x8
 
#define ESCAPED_EMPTY   0x10
 

Enumerations

enum  binary_log::enum_load_dup_handling { binary_log::LOAD_DUP_ERROR = 0, binary_log::LOAD_DUP_IGNORE, binary_log::LOAD_DUP_REPLACE }
 Elements of this enum describe how LOAD DATA handles duplicates. More...
 

Detailed Description

LOAD DATA INFILE is not written to the binary log like other statements.

It is written as one or more events in a packed format, not as a cleartext statement in the binary log. The events indicate what options are present in the statement and how to process the data file.