diff options
author | Alexander Barkov <bar@mariadb.org> | 2017-07-04 14:14:30 +0400 |
---|---|---|
committer | Alexander Barkov <bar@mariadb.org> | 2017-07-04 14:14:30 +0400 |
commit | 25ad623d64ebc34093544875e5b0ebd6101e975b (patch) | |
tree | ee4fb7047a003b0a8c292af0b91e3ef37b870477 /sql/table.cc | |
parent | 760127ac6ff428d4538733b3f99b743f7a802581 (diff) | |
download | mariadb-git-25ad623d64ebc34093544875e5b0ebd6101e975b.tar.gz |
MDEV-13240 Wrong warning with MAX(datetime_field) OVER (...)
The problem resided in Item_window_func implementation,
and it was revealed by bb-10.2-ext specific changes:
Item_window_func::save_in_field() works differently in bb-10.2-ext vs 10.2:
- 10.2 goes through val_str()
- bb-10.2-ext goes through get_date(), due to Type_handler related changes.
get_date() tries to convert empty string to DATETIME, hence the warning.
During a discussion with Vicentiu, it was decided to fix
Item_window_func::val_xxx() to return NULL
(instead of an "empty" value, such as 0 for numbers and '' for strings)
when force_return_blank is set.
Diffstat (limited to 'sql/table.cc')
0 files changed, 0 insertions, 0 deletions