Bug #39837 | SQL_MODE=TRADITIONAL and LOAD DATA LOCAL INFILE does not error | ||
---|---|---|---|
Submitted: | 3 Oct 2008 12:04 | Modified: | 3 Oct 2008 19:56 |
Reporter: | Andy Rigby | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server: Data Types | Severity: | S3 (Non-critical) |
Version: | 5.1.28-rc-community | OS: | Any |
Assigned to: | CPU Architecture: | Any | |
Tags: | SQL_MODE, traditional |
[3 Oct 2008 12:04]
Andy Rigby
[3 Oct 2008 19:56]
Sveta Smirnova
Thank you for taking the time to write to us, but this is not a bug. Please double-check the documentation available at http://dev.mysql.com/doc/ and the instructions on how to report a bug at http://bugs.mysql.com/how-to-report.php Please read at http://dev.mysql.com/doc/refman/5.1/en/load-data.html: If you specify IGNORE, input rows that duplicate an existing row on a unique key value are skipped. If you do not specify either option, the behavior depends on whether the LOCAL keyword is specified. Without LOCAL, an error occurs when a duplicate key value is found, and the rest of the text file is ignored. With LOCAL, the default behavior is the same as if IGNORE is specified; this is because the server has no way to stop transmission of the file in the middle of the operation. Strict mode affects only inserting NULL values into fields defined as NOT NULL