summaryrefslogtreecommitdiff
path: root/mysql-test/t/partition_datatype.test
Commit message (Collapse)AuthorAgeFilesLines
* MDEV-13530 VARBINARY doesn't convert to to BLOB for sizes 65533, 65534 and 65535Alexander Barkov2017-10-131-3/+5
|
* merge with 5.3Sergei Golubchik2011-10-191-7/+7
|\ | | | | | | | | | | | | | | | | | | | | | | | | sql/sql_insert.cc: CREATE ... IF NOT EXISTS may do nothing, but it is still not a failure. don't forget to my_ok it. ****** CREATE ... IF NOT EXISTS may do nothing, but it is still not a failure. don't forget to my_ok it. sql/sql_table.cc: small cleanup ****** small cleanup
* \ mergeMattias Jonsson2011-06-131-0/+310
|\ \
| * | Bug#11746819:Mattias Jonsson2011-03-161-0/+310
| |/ | | | | | | | | | | Bug#28928: UNIX_TIMESTAMP() should be considered unary monotonic by partition pruning Made UNIX_TIMESTAMP MONOTONIC_INCREASING when it have TIMESTAMP argument (only).
* | BUG#48165, needed to introduce length restrictions on partitioning fields to ↵Mikael Ronstrom2009-10-281-3/+6
|/ | | | ensure that no stack overruns occur
* Post push fixunknown2008-02-251-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fixed a missed case in the patch for Bug#31931. Also makes Bug#33722 a duplicate of Bug#31931. Added tests for better coverage. Replaced some legacy function calls. mysql-test/r/partition.result: Added tests for better coverage mysql-test/r/partition_datatype.result: Added tests for better coverage mysql-test/r/partition_error.result: Added tests for better coverage mysql-test/suite/parts/inc/partition_engine.inc: Bug#31931: Mix of handlers error message Bug#33722 is fixed within this patch too mysql-test/suite/parts/r/partition_engine_innodb.result: Bug#31931: Mix of handlers error message Bug#33722 is fixed within this patch too mysql-test/suite/parts/r/partition_engine_myisam.result: Bug#31931: Mix of handlers error message Bug#33722 is fixed within this patch too mysql-test/t/partition.test: Added tests for better coverage mysql-test/t/partition_datatype.test: Added tests for better coverage mysql-test/t/partition_error.test: Added tests for Bug#31931 sql/partition_info.cc: Bug#31931: Mix of handlers error message Fixed case where given info->db_type not matched thd->lex->create_info.db_type And the check for inconsistent subpartition engines-clauses. sql/sql_partition.cc: Changed ha_legacy_type to ha_resolve_storage_engine_name sql/sql_table.cc: Changed ha_legacy_type to ha_resolve_storage_engine_name
* Merge witty.ndb.mysql.com:/Users/mattiasj/clones/mysql-5.1-bug33379unknown2008-02-071-13/+29
|\ | | | | | | | | | | | | | | | | | | into witty.ndb.mysql.com:/Users/mattiasj/clones/51-topush mysql-test/r/partition_datatype.result: Auto merged mysql-test/t/partition_datatype.test: Auto merged
| * Bug#34358: Cannot find specified bit row in partitioned tableunknown2008-02-071-13/+29
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem was incorrect data length in the key_restore function resulting in overwriting the search key. Solution, remove one byte in length if uneven bits are used. mysql-test/r/partition_datatype.result: Bug#34358: Cannot find specified bit row Updated result file mysql-test/t/partition_datatype.test: Bug#34358: Cannot find specified bit row Updated test file (corrected a few errors and added a test case for the bug) sql/key.cc: Bug34358: error in key_restore for bit fields with uneven bits When uneven bits exist, it has special treatment for the uneven bits but does use the same byte again when copying the rest of the key_part.
* | Bug#33379: valgrind error in parts/partition_bit_myisamunknown2008-02-071-10/+10
|/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem was that Field_bit used Field::hash() function that did not know about using null-byte for storing bits. Resulting in wrong length, which was caught by valgrind. Solution: created a Field_bit::hash() that uses Field_bit::val_int() and my_charset_bin-collation function hash_sort. Also use the store function for platform independs mysql-test/r/partition_datatype.result: Bug#33379: valgrind error in parts/partition_bit_myisam result file enabled bit datatype test mysql-test/t/partition_datatype.test: Bug#33379: valgrind error in parts/partition_bit_myisam test file enabled bit datatype test sql/field.cc: Bug#33379: valgrind error in parts/partition_bit_myisam Problem was that Field_bit used Field::hash() function that did not know about using null-byte for storing bits. Resulting in wrong length. Solution: created a Field_bit::hash() that uses Field_bit::val_int() and my_charset_bin-collation function hash_sort. Also use the store function for platform independens. sql/field.h: Bug#33379: valgrind error in parts/partition_bit_myisam Problem was that Field_bit used Field::hash() function that did not know about using null-byte for storing bits. Resulting in wrong length. Solution: created a Field_bit::hash().
* Bug#31705 Partitions: crash if varchar length > 65530unknown2007-11-121-0/+213
Buffer overflow due to wrong key length in partitioning Changed to the correct key_length function. sql/opt_range.cc: Bug#31705 Partitions: crash if varchar length > 65530 Problem: buffer overflow due to wrong key-length Fix: Using correct key_length function mysql-test/r/partition_datatype.result: Bug#31705 Partitions: crash if varchar length > 65530 New test-result case for testing all column types used in key-partitioning. (For verifying correct key-length use) mysql-test/t/partition_datatype.test: Bug#31705 Partitions: crash if varchar length > 65530 New test case for testing all column types used in key-partitioning. (For verifying correct key-length used)
View Lorry Controller Status