6 commits

Author	SHA1	Message	Date
Alexander Barkov	4a7e337e5f	MDEV-28963 Incompatible data type assignment through SP vars is not consistent with columns	2022-06-27 19:52:48 +04:00
Oleksandr Byelkin	2db692f5b4	MDEV-26180: Enable test main.sp-row after the 10.5 merge	2021-08-03 15:44:09 +02:00
Dmitry Shulga	510662e81b	MDEV-16708: more fixes to test cases	2021-06-17 19:30:24 +02:00
Alexander Barkov	061a0f0b8d	MDEV-20175 Move Type_handler_row from Type_collection_std to Type_collection_row	2019-07-25 14:49:33 +04:00
Alexander Barkov	106f0b5798	MDEV-16385 ROW SP variable is allowed in unexpected context ... The problem described in the bug report happened because the code did not test check_cols(1) after fix_fields() in a few places. Additionally, fix_fields() could be called multiple times for SP variables, because they are all fixed at a early stage in append_for_log(). Solution: 1. Adding a few helper methods - fix_fields_if_needed() - fix_fields_if_needed_for_scalar() - fix_fields_if_needed_for_bool() - fix_fields_if_needed_for_order_by() and using it in many cases instead of fix_fields() where the "fixed" status is not definitely known to be "false". 2. Adding DBUG_ASSERT(!fixed) into Item_splocal*::fix_fields() to catch double execution. 3. Adding tests. As a good side effect, the patch removes a lot of duplicate code (~60 lines): if (!item->fixed && item->fix_fields(..) && item->check_cols(1)) return true;	2018-06-05 10:25:39 +04:00
Michael Widenius	a7abddeffa	Create 'main' test directory and move 't' and 'r' there	2018-03-29 13:59:44 +03:00

Renamed from mysql-test/t/sp-row.test (Browse further)