+----------+ | 10 | | 1111111 | +----------+ 2 rows in set (0.00 sec) 

For BIT  values in 0b  binary notation (for example, 0b011010 ), use this SET  clause instead to strip off the leading 0b : 

## Partitioned Table Support 

SET b = CAST(CONV(MID(@var1, 3, LENGTH(@var1)-2), 2, 10) AS UNSIGNED) 

LOAD DATA  supports explicit partition selection using the PARTITION  clause with a list of one or more comma-separated names of partitions, subpartitions, or both. When this clause is used, if any rows from the file cannot be inserted into any of the partitions or subpartitions named in the list, the statement fails with the error Found a row not matching the given partition set . For more information and examples, see Section 24.5, “Partition Selection” . 

## Concurrency Considerations 

With the LOW_PRIORITY  modifier, execution of the LOAD DATA  statement is delayed until no other clients are reading from the table. This affects only storage engines that use only table-level locking (such as MyISAM , MEMORY , and MERGE ). 

With the CONCURRENT  modifier and a MyISAM  table that satisfies the condition for concurrent inserts (that is, it contains no free blocks in the middle), other threads can retrieve data from the table while LOAD DATA is executing. This modifier affects the performance of LOAD DATA  a bit, even if no other thread is using the table at the same time. 

## Statement Result Information 

When the LOAD DATA  statement finishes, it returns an information string in the following format: 

Records: 1 Deleted: 0 Skipped: 0 Warnings: 0 

Warnings occur under the same circumstances as when values are inserted using the INSERT  statement (see Section 13.2.6, “INSERT Statement” ), except that LOAD DATA  also generates warnings when there are too few or too many fields in the input row. 

You can use SHOW WARNINGS  to get a list of the first max_error_count  warnings as information about what went wrong. See Section 13.7.7.42, “SHOW WARNINGS Statement” . 

If you are using the C API, you can get information about the statement by calling the mysql_info() function. See mysql_info(). 

## Replication Considerations 

LOAD DATA  is considered unsafe for statement-based replication. If you use LOAD DATA  with binlog_format=STATEMENT , each replica on which the changes are to be applied creates a temporary file containing the data. This temporary file is not encrypted, even if binary log encryption is active on the source, If encryption is required, use row-based or mixed binary logging format instead, for which replicas do not create the temporary file. For more information on the interaction between LOAD DATA  and replication, see Section 17.5.1.19, “Replication and LOAD DATA” . 

## Miscellaneous Topics 

On Unix, if you need LOAD DATA  to read from a pipe, you can use the following technique (the example loads a listing of the /  directory into the table db1.t1 ): 

