Hi Marc,
marc.alff@stripped wrote:
[..]
> diff -Nrup a/sql/my_decimal.cc b/sql/my_decimal.cc
> --- a/sql/my_decimal.cc 2007-10-11 11:29:06 -06:00
> +++ b/sql/my_decimal.cc 2008-05-13 17:42:38 -06:00
> @@ -41,7 +41,7 @@ int decimal_operation_results(int result
> "", (long)-1);
> break;
> case E_DEC_OVERFLOW:
> - push_warning_printf(current_thd, MYSQL_ERROR::WARN_LEVEL_ERROR,
> + push_warning_printf(current_thd, MYSQL_ERROR::WARN_LEVEL_WARN,
> ER_TRUNCATED_WRONG_VALUE,
> ER(ER_TRUNCATED_WRONG_VALUE),
> "DECIMAL", "");
How this will be elevated to a error when sql_mode is set to
strict_all_tables (traditional)? or, shouldn't we also enforce the
traditional mode on selects too?
--
Davi Arnaut, Software Engineer
MySQL Server Runtime Team
Database Group, Sun Microsystems
