INTO TABLE t1 (column1, column2) SET column3 = CURRENT_TIMESTAMP; 

You can also discard an input value by assigning it to a user variable and not assigning the variable to any table column: 

LOAD DATA INFILE ’file.txt’ INTO TABLE t1 (column1, @dummy, column2, @dummy, column3); 

Use of the column/variable list and SET  clause is subject to the following restrictions: 

•Assignments in the SET  clause should have only column names on the left hand side of assignment operators. 

•You can use subqueries in the right hand side of SET  assignments. A subquery that returns a value to be assigned to a column may be a scalar subquery only. Also, you cannot use a subquery to select from the table that is being loaded. 

•Lines ignored by an IGNORE number  LINES  clause are not processed for the column/variable list or SET  clause. 

•User variables cannot be used when loading data with fixed-row format because user variables do not have a display width. 

## Column Value Assignment 

To process an input line, LOAD DATA  splits it into fields and uses the values according to the column/ variable list and the SET  clause, if they are present. Then the resulting row is inserted into the table. If there are BEFORE INSERT  or AFTER INSERT  triggers for the table, they are activated before or after inserting the row, respectively. 

Interpretation of field values and assignment to table columns depends on these factors: 

•The SQL mode (the value of the sql_mode  system variable). The mode can be nonstrictive, or restrictive in various ways. For example, strict SQL mode can be enabled, or the mode can include values such as NO_ZERO_DATE  or NO_ZERO_IN_DATE . 

•Presence or absence of the IGNORE  and LOCAL  modifiers. 

Those factors combine to produce restrictive or nonrestrictive data interpretation by LOAD DATA : 

•Data interpretation is restrictive if the SQL mode is restrictive and neither the IGNORE  nor the LOCAL modifier is specified. Errors terminate the load operation. 

•Data interpretation is nonrestrictive if the SQL mode is nonrestrictive or the IGNORE  or LOCAL  modifier is specified. (In particular, either modifier if specified overrides  a restrictive SQL mode.) Errors become warnings and the load operation continues. 

Restrictive data interpretation uses these rules: 

•Too many or too few fields results an error. 

•Assigning NULL  (that is, \N ) to a non- NULL  column results in an error. 

•A value that is out of range for the column data type results in an error. 

•Invalid values produce errors. For example, a value such as ’x’  for a numeric column results in an error, not conversion to 0. 

