diff options
| author | Alexander Barkov <bar@mariadb.org> | 2017-05-23 23:11:31 +0400 |
|---|---|---|
| committer | Alexander Barkov <bar@mariadb.org> | 2017-05-23 23:11:31 +0400 |
| commit | 62b62319bf92e9c00da8498fe6e9944a4e43ed7d (patch) | |
| tree | 8ef7a1a94640e51a457246c32295a1aa02551809 /mysql-test/r/sp.result | |
| parent | 6a779a6d28fa69be4c89b72205a11398859f07ca (diff) | |
| download | mariadb-git-62b62319bf92e9c00da8498fe6e9944a4e43ed7d.tar.gz | |
A cleanup for the patch for MDEV-12852, MDEV-12853, MDEV-12869
The patch broke expressions like CAST(1.0e+300 AS SIGNED INT)
in binary protocol, e.g.:
mtr --ps cast
Short real numbers like 1.0e+300 can return huge values,
so using args[0]->max_length is not reliable to choose properly the result
type for Item_func_signed and Item_func_unsigned (between INT and BIGINT).
Setting Item_[un]signed_typecast::max_length to MAX_BIGINT_WIDTH
when doing CAST from FLOAT/DOUBLE, to force type_handler() return
&type_handler_longlong rather than &type_handler_long.
Diffstat (limited to 'mysql-test/r/sp.result')
0 files changed, 0 insertions, 0 deletions