mariadb

Tree: d2f08db40c

Author	SHA1	Message	Date
unknown	d2f08db40c	BUG#20484: "Partitions: crash with EXPLAIN and UNION" - Don't forget to produce "partitions" column for "UNION RESULT" row of EXPLAIN output mysql-test/r/partition_pruning.result: BUG#20484: Testcase mysql-test/t/partition_pruning.test: BUG#20484: Testcase	20 years ago
unknown	4e138572a0	Bug#20086: Can't get data from key partitioned tables with VARCHAR key The problem appeared because the same values produced different hash during INSERT and SELECT for VARCHAR data type. Fix: VARCHAR required special treatment to avoid hashing of length bytes (leftmost one or two bytes) as well as trailing bytes beyond real length, which could contain garbage. Fix is done by introducing hash() - new method in the Field class. mysql-test/r/partition_innodb.result: Adding test case mysql-test/r/partition_pruning.result: Fixing test results (results differ due to changes in hash function) mysql-test/t/partition_innodb.test: Adding test case sql/field.cc: Adding generic hash() method, and a special method for VARCHAR. sql/field.h: Adding prototypes for new methods sql/key.cc: Mark columns for write before executinf of set_key_image(). Thanks for Mikael for suggesting this fix. sql/sql_partition.cc: Removing old hash code. Using new methid field->hash() instead.	20 years ago
unknown	027d90bc58	BUG#19684: Garbage in 'partitions' column in EXPLAIN output: In select_describe(), make the String object that holds the value of "partitions" column to "own" the value buffer, so the buffer isn't prematurely freed. [this is the second attempt with review fixes] mysql-test/r/partition_pruning.result: BUG#19684: Testcase mysql-test/t/partition_pruning.test: BUG#19684: Testcase sql/sql_select.cc: BUG#19684: Garbage in 'partitions' column in EXPLAIN output: - Added comment - Make the String object that holds the value of "partitions" column to "own" the value buffer, so the buffer isn't prematurely freed.	20 years ago
unknown	6ccab8d4de	BUG#19055: There may exist a SEL_TREE objects with type==KEY and keys[i]==NULL for any i. (for example, such objects can be returned from get_mm_parts() for "string_field = int_val). Make find_used_partitions_imerge() to handle such SEL_TREE objects. mysql-test/r/partition_pruning.result: BUG#19055: testcase mysql-test/t/partition_pruning.test: BUG#19055: testcase	20 years ago
unknown	3378a31c6b	BUG#18962: DROP PARTITION fails when partitions dropped for subpartitions with default naming procedure Fixed naming procedures for default partitioning and default subpartitioning mysql-test/r/partition_pruning.result: Fixed test cases for new naming of default subpartitions mysql-test/r/partition_range.result: New test case mysql-test/t/partition_range.test: New test case sql/partition_info.cc: Fixed naming procedures for default partitioning and default subpartitioning sql/partition_info.h: Fixed naming procedures for default partitioning and default subpartitioning	20 years ago
unknown	4e1682ab15	BUG*#17946: New test case for already fixed bug (Problem with LIKE searches for partitioned tables) Added new test case for bug 17946 mysql-test/r/partition_pruning.result: Added new test case for bug 17946 mysql-test/t/partition_pruning.test: Added new test case for bug 17946	20 years ago
unknown	4d1666f6b8	BUG#18558 "Partition pruning results are incorrect for certain class of WHERE clauses" : * Produce right results for conditions that were transformed to "(partitioning_range) AND (list_of_subpartitioning_ranges)": make each partition id set iterator auto-reset itself after it has returned all partition ids in the sequence * Fix "Range mapping" and "Range mapping" partitioning interval analysis functions to correctly deal with NULL values. mysql-test/r/partition_pruning.result: Testcase for BUG#18558 mysql-test/t/partition_pruning.test: Testcase for BUG#18558 sql/opt_range.cc: BUG#18558: Move partition set iterator initialization to sql_partition.cc, comment fixes sql/partition_info.h: BUG#18558: Make each partition set iterator auto-reset itself after it has returned all partition ids in the set it enumerates. sql/sql_partition.cc: BUG#18558: - Make each partition set iterator auto-reset itself after it has returned all partition ids in the set it enumerates. - Fix partition interval analysis to correctly handle intervals with one or both NULL bounds. sql/sql_partition.h: BUG#18558: - Make each partition set iterator auto-reset itself after it has returned all partition ids in the set it enumerates. - Rename PARTITION_ITERATOR::has_null_value to ret_null_part	20 years ago
unknown	a26509aead	BUG#18659: In get_part_iter_for_interval_via_walking(), when we need to obtain partition number, call partition_info->get_part_partition_id() when the table has subpartitions, and get_partition_id() otherwise. (The bug was that we were always doing the latter) mysql-test/r/partition_pruning.result: Testcase for BUG#18659 mysql-test/t/partition_pruning.test: Testcase for BUG#18659	20 years ago
unknown	457510903f	Fix for BUG#18025: Wrong query results because of bugs in partition pruning: - Fix typo bug in SEL_ARG::is_singlepoint() - In set_up_range_analysis_info(), treat MEDIUMINT as enumerable type just like other integer types mysql-test/r/partition_pruning.result: Testcase for BUG#18025 mysql-test/t/partition_pruning.test: Testcase for BUG#18025 sql/opt_range.cc: BUG#18025: Fix a typo bug in SEL_ARG::is_singlepoint() sql/sql_partition.cc: BUG#18025: In set_up_range_analysis_info(), treat MEDIUMINT as enumerable type just like other integer types.	20 years ago
unknown	e737b00134	Someone modified the output to explain but did not run all tests before pushing, otherwise they would have realized that they broke this test. mysql-test/r/partition_pruning.result: Updated results	20 years ago
unknown	4f9e66daa4	WL#2985 "Partition pruning", "do pruning for UPDATE/DELETE": Post-merge fixes	20 years ago
unknown	ff5d012454	WL# 2986 Final patch ----------- This WL is about using this bitmap in all parts of the partition handler. Thus for: rnd_init/rnd_next index_init/index_next and all other variants of index scans read_range_... the various range scans implemented in the partition handler. Also use those bitmaps in the various other calls that currently loop over all partitions. mysql-test/r/partition_pruning.result: WL# 2986 New results reflecting bitmap being used to determine if a partition is to be included mysql-test/t/partition_pruning.test: WL# 2986 New tests to show bitmap being used in ha_partition sql/ha_partition.cc: WL# 2986 Used work from 2682 and removed the partition select code. Added do {} while loop to any iteration over partitions to now utilise m_part_info->used_partitions bitmap to determine if a partition should be used. sql/ha_partition.h: WL# 2986 Removed unused member sql/handler.h: WL# 2986 Removed unused member sql/opt_range.cc: WL# 2986 Added bitmap_clear_all to clear bitmap prior to pruning DBUG code for testing sql/sql_partition.cc: WL# 2986 Changed < to <=, which fixes the problem with edge cases going awry.	20 years ago
unknown	d50236f69e	WL#2985 "Partition pruning": addition2: perform partition pruning for single-table UPDATE/DELETE. mysql-test/r/partition_pruning.result: WL#2985 "Partition pruning": addition2: perform partition pruning for UPDATE/DELETE: testcases added mysql-test/t/partition_pruning.test: WL#2985 "Partition pruning": addition2: perform partition pruning for UPDATE/DELETE: testcases added sql/sql_delete.cc: WL#2985 "Partition pruning": addition2: perform partition pruning for UPDATE/DELETE: Added partition pruning call in mysql_delete() sql/sql_update.cc: WL#2985 "Partition pruning": addition2: perform partition pruning for UPDATE/DELETE: Added partition pruning call in mysql_update()	20 years ago
unknown	dc2a6e226d	WL#2985 "Partition Pruning": - post-...-post review fixes - Added "integer range walking" that allows to do partition pruning for "a <=? t.field <=? b" by finding used partitions for a, a+1, a+2, ..., b-1, b. mysql-test/r/partition_pruning.result: WL#2985 "Partition Pruning": tests for "integer range walking" mysql-test/t/partition.test: WL#2985 "Partition Pruning": post-review fixes mysql-test/t/partition_pruning.test: WL#2985 "Partition Pruning": tests for "integer range walking" sql/handler.h: WL#2985 "Partition Pruning": "integer range walking": - class partition_info now has pointers to "partitioning interval analysis" functions - added "partition set iterator" definitions. sql/opt_range.cc: WL#2985 "Partition Pruning": "integer range walking": - Switched to use "partitioning interval analysis" functions - Fixed two problems in find_used_partitions() that occur on complicated WHERE clauses. sql/sql_partition.cc: WL#2985 "Partition Pruning": "integer range walking": - Added "partitioning interval analysis" functions: get_part_iter_for_interval_via_mapping, get_part_iter_for_interval_via_walking, - Added appropriate partition-set-iterator implementations - Added a function to set up Partitioning Interval Analysis-related fields in partition_info. sql/sql_select.cc: WL#2985 "Partition pruning": added comments.	20 years ago
unknown	78d1abbaf9	WL#2985 "Partition Pruning": post-review fixes: Better comments mysql-test/r/partition_pruning.result: WL#2985 "Partition Pruning": more tests mysql-test/t/partition_pruning.test: WL#2985 "Partition Pruning": more tests sql/handler.h: WL#2985 "Partition Pruning": post-review fixes: comments	20 years ago
unknown	01e1d1a0af	add missing DROP TABLE [IF EXISTS] clauses	20 years ago
unknown	a4a1bb0e2f	WL#2985 "Partition Pruning": post-review fixes: - Added more comments. - Added a RANGE_OPT_PARAM::remove_jump_scans flag that disables construction of index_merge SEL_TREEs that represent unusable conditions like "key1part1<c1 OR key2part2<c2" - make prune_partitions() function handle the case where range analysis produces a list of index_merge trees (it turned out that this is possible, appropriate test case added). - Other small fixes. mysql-test/r/partition_pruning.result: WL#2985 "Partition Pruning": post-review fixes: more test cases mysql-test/t/partition_pruning.test: WL#2985 "Partition Pruning": post-review fixes: more test cases sql/opt_range.cc: WL#2985 "Partition Pruning": post-review fixes: - Added more comments. - Fix the debug printouts - Added a RANGE_OPT_PARAM::remove_jump_scans flag that disables construction of index_merge SEL_TREEs that represent unusable conditions like "key1part1<c1 OR key2part2<c2" - make prune_partitions() function handle the case where range analysis produces a list of index_merge trees (it turned out that this is possible, appropriate test case added). sql/sql_partition.cc: WL#2985 "Partition Pruning": post-review fixes: make requested edits in comments. sql/table.h: WL#2985 "Partition Pruning": post-review fixes: added bool TABLE::no_partitions_used (this change was missed when making the original cset)	20 years ago
unknown	f19fb8709c	WL#2985 "Partition Pruning" sql/ha_ndbcluster.cc: WL#2985 "Partition Pruning": added part_info->used_partitions initialization sql/ha_partition.cc: WL#2985 "Partition Pruning": added part_info->used_partitions initialization sql/handler.h: WL#2985 "Partition Pruning": Added function prototypes in partition_info: - Added 'used_partitions' bitmap - Added comments sql/item.h: WL#2985 "Partition Pruning": - added enum monotonicity_info - added virtual Item::get_monotonicity_info() sql/item_timefunc.cc: WL#2985 "Partition Pruning": - added Item_func_to_days::get_monotonicity_info() - added Item_func_year::get_monotonicity_info() sql/item_timefunc.h: WL#2985 "Partition Pruning": - added Item_func_to_days::get_monotonicity_info() - added Item_func_year::get_monotonicity_info() sql/opt_range.cc: WL#2985 "Partition Pruning": - Split out PARAM structure into PARAM and RANGE_OPT_PARAM part. - Added partition pruning module code. sql/opt_range.h: WL#2985 "Partition Pruning": Added prune_partitions() function declaration. This is the entry point for partition pruning module sql/sql_class.cc: WL#2985 "Partition Pruning": added support for "EXPLAIN PARTITIONS SELECT ..." sql/sql_lex.h: WL#2985 "Partition Pruning": added support for "EXPLAIN PARTITIONS SELECT ..." sql/sql_partition.cc: WL#2985 "Partition Pruning": - Added get_list_array_idx_for_endpoint and get_range_... functions to support partition pruning on "partition_field < const"-like intervals. - Added partition_info::used_partitions bitmap. - Added make_used_partitions_str function - Fixed BUG#15819 sql/sql_select.cc: WL#2985 "Partition Pruning": - Added prune_partitions() invocation right before the range analysis - Added code to handle return value from prune_partitions() - Added support for "EXPLAIN PARTITIONS SELECT ..." sql/sql_yacc.yy: #2985 "Partition Pruning": added support for "EXPLAIN PARTITIONS SELECT ..."	20 years ago

20 Commits (d2f08db40c90a0b0ffd8fe84cda99fbb9af0c6c9)