diff options
| author | Sergei Golubchik <serg@mariadb.org> | 2017-04-03 17:18:37 +0200 |
|---|---|---|
| committer | Sergei Golubchik <serg@mariadb.org> | 2017-04-07 09:55:54 +0200 |
| commit | 82196f0131a26c0f72e7452ff172eb2f93067efd (patch) | |
| tree | e122314d7c335aefaffc2e48ee81c18f90c4f158 /sql/sql_table.cc | |
| parent | 30cbbfbf774b4795ac70d7ca333f37f402a9184d (diff) | |
| download | mariadb-git-82196f0131a26c0f72e7452ff172eb2f93067efd.tar.gz | |
MDEV-11995 ALTER TABLE proceeds despite reporting ER_TOO_LONG_KEY error
automatic shortening of a too-long non-unique key should
be not a warning, but a note. It's a normal optimization,
doesn't affect correctness, and should never be converted to
an error, no matter how strict sql_mode is.
Diffstat (limited to 'sql/sql_table.cc')
| -rw-r--r-- | sql/sql_table.cc | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/sql/sql_table.cc b/sql/sql_table.cc index baab8e320a0..f5f2ffb0b63 100644 --- a/sql/sql_table.cc +++ b/sql/sql_table.cc @@ -3949,7 +3949,7 @@ mysql_prepare_create_table(THD *thd, HA_CREATE_INFO *create_info, if (key->type == Key::MULTIPLE) { /* not a critical problem */ - push_warning_printf(thd, Sql_condition::WARN_LEVEL_WARN, + push_warning_printf(thd, Sql_condition::WARN_LEVEL_NOTE, ER_TOO_LONG_KEY, ER_THD(thd, ER_TOO_LONG_KEY), key_part_length); |