This problem occured because the reorganization of the list of values when the
number of elements exceeds 32 was not handled correctly. I have fixed the
problem by fixing the way that the list values are reorganized when the number
of list values exceeds 32.
Author:
Jacob Mathew.
Reviewer:
Alexey Botchkov.
Merged From:
Commit 8e01598 on branch bb-10.3-MDEV-16101
Added new test cases, fixed bugs in relation to those
mysql-test/r/partition_charset.result:
New test case
mysql-test/r/partition_list.result:
New test case
mysql-test/t/partition_list.test:
New test case
sql/partition_info.cc:
Missing initialisation
sql/sql_partition.cc:
key_restore made use of field->ptr in VARCHAR fields and
when used with REPLACE it caused the key_restore to
become against table->record[0] when buf pointed to
table->record[1]
mysql-test/t/partition_charset.test:
New test case from bug report
mysql-test/t/partition_list.test:
New test case from bug report
mysql-test/r/partition_bug18198.result:
New test case
mysql-test/t/partition_bug18198.test:
New test case
Problem was with handling NULL values in ranges
mysql-test/r/partition_hash.result:
New partition pruning test cases
mysql-test/r/partition_list.result:
New partition pruning test cases
mysql-test/r/partition_pruning.result:
New partition pruning test cases
mysql-test/r/partition_range.result:
New partition pruning test cases
mysql-test/t/partition_hash.test:
New partition pruning test cases
mysql-test/t/partition_list.test:
New partition pruning test cases
mysql-test/t/partition_pruning.test:
New partition pruning test cases
mysql-test/t/partition_range.test:
New partition pruning test cases
sql/opt_range.cc:
Added comment
sql/sql_partition.cc:
Partition pruning didn't handle ranges with NULL values in a proper manner
mysql-test/r/partition_list.result:
New test case
mysql-test/t/partition_list.test:
New test case
sql/ha_partition.cc:
Implement a proper update_create_info
Bug # 17894 - Comparison with "less than" operator fails with range partition
The problem here was that on queries such as < 3, the range given is NULL < n < 3.
The null part works correctly where the null value is stored in rec[0] and the
field is marked as being null. However, when the 3 is processed, the 3 is places
on rec[0] but the null flag is left uncleared.
partition_range.result:
Results block for bug #17894
partition_range.test:
Test block for bug #17894
partition_list.result:
Results block for bug #17173
partition_list.test:
Test block for bug #17173
opt_range.cc:
call set_notnull to clear any null flag that may have been set
sql/opt_range.cc:
call set_notnull to clear any null flag that may have been set
mysql-test/t/partition_list.test:
Test block for bug #17173
mysql-test/r/partition_list.result:
Results block for bug #17173
mysql-test/t/partition_range.test:
Test block for bug #17894
mysql-test/r/partition_range.result:
Results block for bug #17894
mysql-test/r/partition_list.result:
test result fixed
mysql-test/r/partition_range.result:
test result fixed
mysql-test/t/partition_list.test:
test fixed
mysql-test/t/partition_range.test:
test fixed
