Bug #27156 | Not even if strict mode will halt on warnings | ||
---|---|---|---|
Submitted: | 14 Mar 2007 23:33 | Modified: | 6 Nov 2010 17:37 |
Reporter: | Stephen Gornick | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Server: Data Types | Severity: | S3 (Non-critical) |
Version: | 5.0, 5.1, 5.6.99 | OS: | Linux (Linux) |
Assigned to: | CPU Architecture: | Any | |
Tags: | client, client, error, errors, execute, Execution, force, halt, halted, mode, mode, SQL, sql mode, SQL_MODE, stop, stopped, strict, strict mode, strict_all_tables, strict_trans_tables, traditional, warning, warnings |
[14 Mar 2007 23:33]
Stephen Gornick
[14 Mar 2007 23:43]
Stephen Gornick
test.sql
Attachment: test.sql (application/octet-stream, text), 410 bytes.
[14 Mar 2007 23:48]
Stephen Gornick
Running test.sql as a script, $ mysql -uroot -p < test.sql Warning (Code 1052): Column 'col1' in group statement is ambiguous col1 test 123 which shows that execution didn't stop after the warning.
[6 Nov 2010 17:37]
Sveta Smirnova
Thank you for the report. Verified as described. Also there is inconsistency when one inserts integer into varchar filed: create table test.z (col1 varchar(10)) engine=innodb; insert into test.z values (123); -- success!
[9 Nov 2010 19:37]
Konstantin Osipov
Sveta, there is no issue with your test since there is no truncation.
[9 Nov 2010 19:48]
Sveta Smirnova
Kostja, correct. But type conversion still exists. we should have at least a note at "type conversion rules" in our user manual about this silent type conversion.