diff options
| author | unknown <evgen@moonbone.local> | 2006-03-10 13:53:00 +0300 |
|---|---|---|
| committer | unknown <evgen@moonbone.local> | 2006-03-10 13:53:00 +0300 |
| commit | 50c8c206fca3ea3b7ca6978ba1fe283f9777db4d (patch) | |
| tree | 6c05e6aa6a49c9c2619900213286e323e74e1da4 /mysql-test/r/view_grant.result | |
| parent | 58bf749f439e7eb828206b3d39da42372c7b178b (diff) | |
| download | mariadb-git-50c8c206fca3ea3b7ca6978ba1fe283f9777db4d.tar.gz | |
Fixed bug#13575: SP funcs in select with distinct/group and order by can
produce wrong data
By default Item_sp_func::val_str() returns string from it's result_field
internal buffer. When grouping is present Item_copy_string is used to
store SP function result, but it doesn't additionally buffer the result.
When the next record is read, internal buffer is overwritten, due to
this Item_copy_string::val_str() will have wrong data. Thus producing
weird query result.
The Item_func_sp::val_str() now makes a copy of returned value to prevent
occasional corruption.
mysql-test/t/sp.test:
Added test case for bug#13575: SP funcs in select with distinct/group and order by can
produce wrong data
mysql-test/r/sp.result:
Added test case for bug#13575: SP funcs in select with distinct/group and
order by can produce wrong data
sql/item_func.h:
Fixed bug#13575: SP funcs in select with distinct/group and order by can
produce wrong data
The Item_func_sp::val_str() now makes a copy of returned value to prevent
occasinal corruption.
Diffstat (limited to 'mysql-test/r/view_grant.result')
0 files changed, 0 insertions, 0 deletions