Fix for bug #30885: MEMORY returns incorrect data if BTREE index is used for NULL lookup
Problem: creating an rb-tree key we store length (2 bytes) before the actual data for varchar key parts. The fact was missed for NULL key parts, when we set NULL byte and skip the rest. Fix: take into account the length of the varchar key parts for NULLs. heap/hp_hash.c: Fix for bug #30885: MEMORY returns incorrect data if BTREE index is used for NULL lookup - skip varchar key parts length (2 byte) for null key parts. mysql-test/r/heap_btree.result: Fix for bug #30885: MEMORY returns incorrect data if BTREE index is used for NULL lookup -test result. mysql-test/t/heap_btree.test: Fix for bug #30885: MEMORY returns incorrect data if BTREE index is used for NULL lookup - test case.
Showing
Please register or sign in to comment