summaryrefslogtreecommitdiff
path: root/mysql-test/t/partition_column.test
Commit message (Collapse)AuthorAgeFilesLines
* Bug#52815: LIST COLUMNS doesn't insert rows in correctMattias Jonsson2010-04-211-0/+26
| | | | | | | | | | | | | | | | | | | | | | | | | | | partition if muliple columns used Problem was that range scanning through the sorted array of the column list values did not use a correct index calculation. Fixed by also taking the number of columns in the calculation. mysql-test/r/partition_column.result: Bug#52815: LIST COLUMNS doesn't insert rows in correct partition if muliple columns used Added test result for bug. mysql-test/t/partition_column.test: Bug#52815: LIST COLUMNS doesn't insert rows in correct partition if muliple columns used Added test for bug. sql/sql_partition.cc: Bug#52815: LIST COLUMNS doesn't insert rows in correct partition if muliple columns used list_col_array is a matrix of field values, so one must also use the number of columns to calculate the correct partition id.
* Bug#51347: assertion with show create table + partition by columnsMattias Jonsson2010-03-041-12/+53
| | | | | | | | | | | | | | | | | | | | | | | | | | | on decimal column The problem was that there was no check to disallow DECIMAL columns in the code (it was accepted as if it was INTEGER). Solution was to correctly disallow DECIMAL columns in COLUMNS partitioning. As documented. mysql-test/r/partition_column.result: Bug#51347: assertion with show create table + partition by columns on decimal column updated test result mysql-test/t/partition_column.test: Bug#51347: assertion with show create table + partition by columns on decimal column Added test to verify column types that is not supported sql/sql_partition.cc: Bug#51347: assertion with show create table + partition by columns on decimal column Moved DECIMAL types to be disallowed as column types in COLUMNS partitioning
* Bug#48737: Partitions: search fails with ucs2Mattias Jonsson2009-12-211-0/+17
| | | | | | | | | | | | | | | | Recommit of patch: http://lists.mysql.com/commits/91400 Test case only (code part was pushes as bug-49028) mysql-test/r/partition_column.result: Bug#48737: Partitions: search fails with ucs2 added test case mysql-test/t/partition_column.test: Bug#48737: Partitions: search fails with ucs2 Added result
* BUG#49180, fixed MAXVALUE problemMikael Ronstrom2009-12-021-1/+16
|
* Review fixes for BUG#48161 and BUG#48447Mikael Ronstrom2009-11-061-10/+6
|
* BUG#48447, BUG#48161, fixed a regression from fix of BUG#6045, where binary ↵Mikael Ronstrom2009-11-051-0/+35
| | | | collations can use indexes/partition pruning for cases using equality conditions, however it cannot be used for any other condition like <, >, <=, >=, <>, also added test case for verification of BUG#47774 in this patch
* Fixed a few bugs in hex string generation, in call to val_str for partition ↵Mikael Ronstrom2009-11-021-28/+6
| | | | expressions, also made code reusable for DEFAULT handling to fix BUG#48464 by introducing function get_cs_converted_string_value, added partition_utf8 test case for UTF8 outputs
* Added test case for UTF8 strings in partition constantsMikael Ronstrom2009-11-021-0/+2
|
* Fixed such that we fail if using integer constants for character set fields, ↵Mikael Ronstrom2009-10-301-1/+11
| | | | now need to have correct constant types
* Fixed so that character set constants are encoded as hex strings in frm ↵Mikael Ronstrom2009-10-301-1/+0
| | | | file, but as utf8 strings in the same manner as default values in show create table and information schema tables
* Changed COLUMN_LIST to COLUMNS after arch reviewMikael Ronstrom2009-10-291-37/+37
|
* Fixed code review change to ensure that VALUES constants are of the same ↵Mikael Ronstrom2009-10-281-2/+2
| | | | result type as the field they are constants for
* BUG#48165, needed to introduce length restrictions on partitioning fields to ↵Mikael Ronstrom2009-10-281-0/+17
| | | | ensure that no stack overruns occur
* Fixed sql_mode issue in BUG#48164, will ignore sql_mode when generating ↵Mikael Ronstrom2009-10-281-0/+15
| | | | constants, also warnings will not be tolerated
* BUG#46183, added character set identifier on character constants in VALUES ↵Mikael Ronstrom2009-10-221-11/+13
| | | | part for column list partitioned tables to ensure constants are handled properly according to character sets
* A lot of fixes to make character set work ok, first step to fixing BUG#48163Mikael Ronstrom2009-10-221-12/+47
|
* Added checks for no NULL values in VALUES LESS THAN, added tests for no ↵Mikael Ronstrom2009-10-211-5/+15
| | | | MAXVALUE in VALUES IN
* MergeMikael Ronstrom2009-10-211-0/+12
|\
| * Fixed Information schema for column list partitioned tablesMikael Ronstrom2009-10-211-0/+12
| |
* | Fixed removal of column_list keyword for VALUES part, retained for PARTITION ↵Mikael Ronstrom2009-10-161-67/+64
|/ | | | BY RANGE/LIST COLUMN_LIST, not entirely working yet
* BUG#47837, Duplicate field names were allowed in both column list ↵Mikael Ronstrom2009-10-061-0/+11
| | | | partitioning and key partitioning, added check to give error in this case
* BUG#47838, NULL values in ranges was dropped due to missing else part in ↵Mikael Ronstrom2009-10-061-0/+27
| | | | store_tuple_to_record
* BUG#47754, used number of parts instead of number of list values as end part ↵Mikael Ronstrom2009-10-021-0/+5
| | | | for list partitioning in column list partitioning
* Added more test casesMikael Ronstrom2009-10-011-0/+19
|
* Changed all no_ to num_ to avoid strange names like no_list_values which is ↵Mikael Ronstrom2009-10-011-0/+32
| | | | not expected to be number of list values, rather a boolea indicating no list values
* WL#3352, Introducing Column list partitioning, makes it possible to ↵Mikael Ronstrom2009-09-151-0/+209
partition on most data types, makes it possible to prune on multi-field partitioning
View Lorry Controller Status