summaryrefslogtreecommitdiff
path: root/mysql-test
Commit message (Collapse)AuthorAgeFilesLines
* Merging TO_BASE64() and FROM_BASE64() from MySQL-5.6Alexander Barkov2013-09-234-4/+1667
|
* MDEV-4879 - Merge test cases for new CREATE TEMPORARY TABLE privilege modelSergey Vojtovich2013-09-2014-0/+1398
| | | | | | | | - merged test cases for MySQL bug#27480 - fixed that LOCK TABLES was unable to open temporary table (covered by grant2 test, merged appropriate code from 5.6) - commented lines that cause server crash in merge test, reported MDEV-5042 (not relevant to bug#27480)
* 10.0-base merge.Sergei Golubchik2013-09-21163-683/+5061
|\ | | | | | | | | Partitioning/InnoDB changes are *not* merged (they'll come from 5.6) TokuDB does not compile (not updated to 10.0 SE API)
| * 5.5.33a mergeSergei Golubchik2013-09-206-1/+21
| |\
| | * MDEV-5029 Crash in MariaDB 5.5.33 with .frm from older MariaDB releaseSergei Golubchik2013-09-186-1/+21
| | | | | | | | | | | | | | | Don't fail when an frm is inconsistent (legacy DB_TYPE_xxx code doesn't match the engine name), use the engine name, ignore the legacy code.
| * | mergeSergei Golubchik2013-09-1899-281/+2623
| |\ \
| | * \ 5.5 merge and fixes for compiler/test errorsSergei Golubchik2013-09-1899-281/+2623
| | |\ \ | | | |/
| | | * MDEV-5029 Crash in MariaDB 5.5.33 with .frm from older MariaDB releaseSergei Golubchik2013-09-183-0/+13
| | | | | | | | | | | | | | | | | | | | | | | | don't set TABLE_SHARE::keys before TABLE_SHARE::key_info is set, otherwise an error might leave only the first property set and it will confuse TABLE_SHARE::destroy()
| | | * Merge from 5.3Alexander Barkov2013-09-161-1/+1
| | | |\ | | | | | | | | | | | | | | | | | | | | | | | | | pending merges: Alexander Barkov 2013-09-16 backport from 10.0
| | | | * backport from 10.0Alexander Barkov2013-09-161-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | mtr can crash occasionally. This happens when mtr sends to a child mtr process (or vice-versa) a packet, that gets truncated or, perhaps, split in two. Then the other side cannot deserialize it and fails as above.
| | | * | Merge from 5.3Alexander Barkov2013-09-162-0/+41
| | | |\ \ | | | | |/
| | | | * MDEV-4861 TIME/DATETIME arithmetics does not preserve INTERVAL precisionAlexander Barkov2013-09-162-0/+41
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Adding tests only. The problem was earlier fixed by MDEV-4724 Some temporal functions do not preserve microseconds
| | | * | Merge from 5.3Alexander Barkov2013-09-162-0/+74
| | | |\ \ | | | | |/ | | | | | | | | | | | | | | | | | | | | pending merges: Alexander Barkov 2013-09-16 MDEV-4870 Wrong values of CASE, COALESCE, IF...
| | | | * MDEV-4870 Wrong values of CASE, COALESCE, IFNULL on a combination of ↵Alexander Barkov2013-09-162-0/+74
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | different temporal types Adding test cases from the bug report only. The problem was earlier fixed by: MDEV-4863 COALESCE(time_or_datetime) returns wrong results in numeric context modified: mysql-test/r/func_time.result mysql-test/t/func_time.test
| | | * | Merge from 5.3Alexander Barkov2013-09-162-0/+12
| | | |\ \ | | | | |/ | | | | | | | | | | | | | | | | | | | | pending merges: Alexander Barkov 2013-09-16 MDEV-4869 Wrong result of MAKETIME(0, 0, -0.1)
| | | | * MDEV-4869 Wrong result of MAKETIME(0, 0, -0.1)Alexander Barkov2013-09-162-0/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Adding a test case only. The problem was fixed by: MDEV-4724 Some temporal functions do not preserve microseconds modified: mysql-test/r/func_time.result mysql-test/t/func_time.test
| | | * | Merge from 5.3Alexander Barkov2013-09-162-0/+100
| | | |\ \ | | | | |/ | | | | | | | | | | | | | | | | | | | | pending merges: Alexander Barkov 2013-09-16 MDEV-4843 Wrong data type for TIMESTAMP('200...
| | | | * MDEV-4843 Wrong data type for TIMESTAMP('2001-01-01','10:10:10')Alexander Barkov2013-09-162-0/+100
| | | | |
| | | * | Merge 5.3->5.5Igor Babaev2013-09-152-0/+33
| | | |\ \ | | | | |/
| | | | * Fixed bug mdev-5015.Igor Babaev2013-09-152-0/+33
| | | | | | | | | | | | | | | | | | | | | | | | | The patch for mdev-4355 had a defect: the cached values for bitmaps of used tables were not updated when processing degenerate OR formulas.
| | | | * MDEV-4724 Some temporal functions do not preserve microsecondsAlexander Barkov2013-09-1313-123/+334
| | | | |
| | | * | MDEV-5012 Server crashes in Item_ref::real_item on EXPLAIN with select ↵Sergei Golubchik2013-09-132-0/+26
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | subqueries or views, constant table, derived_merge+derived_with_keys revert incorrect change, merged from mysql-5.5
| | | * | merge 5.3->5.5unknown2013-09-132-2/+57
| | | |\ \ | | | | |/
| | | | * MDEV-5005: Subquery in Procedure somehow affecting temporary tableunknown2013-09-122-0/+55
| | | | | | | | | | | | | | | | | | | | Removed unneeded set of TABLE_LIST::skip_temporary flag.
| | | * | Merge from 5.3.Alexander Barkov2013-09-1318-173/+384
| | | |\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | pending merges: Alexander Barkov 2013-09-12 MDEV-4724 Some temporal functions do not pre...
| | | | * | MDEV-4724 Some temporal functions do not preserve microsecondsAlexander Barkov2013-09-1213-123/+334
| | | | | |
| | | * | | Merge 5.3 -> 5.5Sergey Petrunya2013-09-123-0/+24
| | | |\ \ \ | | | | | |/ | | | | |/|
| | | | * | MDEV-5011: ERROR Plugin 'MEMORY' has ref_count=1 after shutdown for SJM queriesSergey Petrunya2013-09-123-0/+24
| | | | |/ | | | | | | | | | | | | | | | | | | | | - Provide a special execution path for cleanup of degenerate non-merged semi-join children of degenerate selects.
| | | * | support ./mtr suite.test,com,bi,na,tions syntaxSergei Golubchik2013-09-111-10/+27
| | | | |
| | | * | merge with 5.5-tokudb tree. In particular:Sergei Golubchik2013-09-1014-42/+20
| | | |\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * add TokuDB, together with the ft-index library * cmake support, auto-detecting whether tokudb can be built * fix packaging - tokudb-engine.rpm, deb * remove PBXT * add jemalloc * the server is built with jemalloc by default even if TokuDB is not built * documentation files in RPM are installed in the correct location * support for optional deb packages (tokudb has specific build requirements) * move plugins from mariadb-server deb to appropriate debs (server/test/libmariadbclient) * correct mariadb-test.deb to be not architecture-independent * fix out-of-tree builds to never modify in-tree files * new handler::prepare_index_scan() method
| | | | * | fixes for out-of-source buildsSergei Golubchik2013-09-091-10/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | mysql-test/CMakeLists.txt: don't generate collection fules. we don't use them and they break out-of-source builds
| | | | * | remove PBXTSergei Golubchik2013-08-3013-32/+10
| | | | | |
| | | * | | fix insert.test in --ps-protocol.Sergei Golubchik2013-09-101-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | After MDEV-4817, WHERE clause may be evaluated early, in fix_fields. In ps-protocol fix_fields happens both for prepare and execute phase, generating double the number of warnings from the early WHERE clause executions.
| | | * | | Merge from 5.3Alexander Barkov2013-09-103-7/+204
| | | |\ \ \ | | | | | |/ | | | | |/| | | | | | | | | | | | | | | | | | | pending merges: Alexander Barkov 2013-09-09 MDEV-4863 COALESCE(time_or_datetime) returns...
| | | | * | MDEV-4863 COALESCE(time_or_datetime) returns wrong results in numeric contextAlexander Barkov2013-09-093-7/+204
| | | | | |
| | | * | | mysql-5.5.33 mergeSergei Golubchik2013-09-0615-39/+182
| | | |\ \ \
| | | | * \ \ merge 5.1 => 5.5Tor Didriksen2013-07-012-4/+6
| | | | |\ \ \
| | | | | * | | Bug#58165: "my_empty_string" gets modified and causes LOAD DATA to fail andTor Didriksen2013-07-012-4/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Cleanup test case (left outfile in data dir)
| | | | * | | | Bug #16996656: UNIQUE OPTION PREFIXES NOT DEPRECATED IN 5.5+Georgi Kodinov2013-06-265-19/+19
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Backported the deprecation warnings from WL#6978 to 5.5
| | | | * | | | Bug#13548704 ALGORITHM USED FOR DROPPING PARTITIONED TABLE CAN LEADAditya A2013-06-142-5/+4
| | | | |\ \ \ \ | | | | | |/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | TO INCONSISTENCY [Merge from 5.1]
| | | | | * | | Bug#13548704 ALGORITHM USED FOR DROPPING PARTITIONED TABLE CAN LEADAditya A2013-06-142-5/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | TO INCONSISTENCY PROBLEM -------- When we drop a partitoned table , we first gather the information about partitions in the table from the table_name.par file and store it in an internal data structure.Then we delete this file and the data in the table. If the server crashes after deleting the file,then after recovering we cannot access the table .Even we cannot drop the table ,because drop algorithm requires par file to read the partition information. FIX --- 1. We move the part of deleting par file after deleting all the table data from the storage egine. 2. During drop operation if we detect that the par file is missing then we delete the .frm file,since there is no way of recovering without par file. [Approved by Mattias rb#2576 ]
| | | | * | | | Bug #16917425 -DBUILD_CONFIG=MYSQL_RELEASE -DWITH_DEBUG=ON FAILS 4 AND ↵Olav Sandstaa2013-06-071-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | SKIPS 27 MTR TESTS Revert fix since it caused mtr tests to not run in pushbuild.
| | | | * | | | Bug #16917425 -DBUILD_CONFIG=MYSQL_RELEASE -DWITH_DEBUG=ON FAILS 4 AND ↵sayantan dutta2013-06-071-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | SKIPS 27 MTR TESTS
| | | | * | | | Bug#16765278 DELETE SQL_LOAD_MB* FILE (TEMP FILE) CREATEDVenkatesh Duggirala2013-05-241-5/+4
| | | | |\ \ \ \ | | | | | |/ / / | | | | | | | | | | | | | | | | | | | | | | | | BY BINLOG_KILLED_SIMULATE.TEST Merging fix from mysql-5.1
| | | | | * | | Bug#16765278 DELETE SQL_LOAD_MB* FILE (TEMP FILE) CREATEDVenkatesh Duggirala2013-05-241-6/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | BY BINLOG_KILLED_SIMULATE.TEST 'mysqbinlog' tool creates a temporary file while preparing LOAD DATA QUERY. These files needs to be deleted at the end of the test script otherwise these files are left out in the daily-run machines, causing "no space on device issues" Fix: Delete them at the end of these test scripts 1) execute mysqlbinlog with --local-load option to create these files in a specified tmpdir 2) delete the tmpdir at the end of the test script
| | | | | * | | Bug #16813007 - MTR IS NOT TAKING MYSQLTEST CLIENT USING THE ENV VARIABLE ↵sayantan dutta2013-05-161-1/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | MYSQL_TEST
| | | | * | | | Bug#16194302: SUPPORT FOR FLOATING-POINT SYSTEM VARIABLESAshish Agarwal2013-05-192-1/+133
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | USING THE PLUGIN INTERFACE. ISSUE: No support for floating-point plugin system variables. SOLUTION: Allowing plugins to define and expose floating-point system variables of type double. MYSQL_SYSVAR_DOUBLE and MYSQL_THDVAR_DOUBLE are added. ISSUE: Fractional part of the def, min, max values of system variables are ignored. SOLUTION: Adding functions that are used to store the raw representation of a double in the raw bits of unsigned longlong in a way that the binary representation remains the same.
| | | | * | | | Bug 16813007 5.1 => 5.5sayantan dutta2013-05-161-1/+11
| | | | |\ \ \ \
| | | | | * | | | Bug #16813007 - MTR IS NOT TAKING MYSQLTEST CLIENT USING THE ENV VARIABLE ↵sayantan dutta2013-05-161-1/+11
| | | | | |/ / / | | | | | | | | | | | | | | | | | | | | | | | | MYSQL_TEST
| | | | * | | | Bug#12328597 - MULTIPLE COUNT(DISTINCT) IN SAME SELECT FALSE Neeraj Bisht2013-05-132-2/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | WITH COMPOSITE KEY COLUMNS Problem:- While running a SELECT query with several AGGR(DISTINCT) function and these are referring to different field of same composite key, Returned incorrect value. Analysis:- In a table, where we have composite key like (a,b,c) and when we give a query like select COUNT(DISTINCT b), SUM(DISTINCT a) from .... here, we first make a list of items in Aggr(distinct) function (which is a, b), where order of item doesn't matter. and then we see, whether we have a composite key where the prefix of index columns matches the items of the aggregation function. (in this case we have a,b,c). if yes, so we can use loose index scan and we need not perform duplicate removal to distinct in our aggregate function. In our table, we traverse column marked with <-- and get the result as (a,b,c) count(distinct b) sum(distinct a) treated as count b treated as sum(a) (1,1,2)<-- 1 1 (1,2,2)<-- 1++=2 1+1=2 (1,2,3) (2,1,2)<-- 2++=3 1+1+2=4 (2,2,2)<-- 3++=4 1+1+2+2=6 (2,2,3) result will be 4,6, but it should be (2,3) As in this case, our assumption is incorrect. If we have query like select count(distinct a,b), sum(distinct a,b)from .. then we can use loose index scan Solution:- In our query, when we have more then one aggr(distinct) function then they should refer to same fields like select count(distinct a,b), sum(distinct a,b) from .. -->we can use loose scan index as both aggr(distinct) refer to same fields a,b. If they are referring to different field like select count(distinct a), sum(distinct b) from .. -->will not use loose scan index as both aggr(distinct) refer to different fields.
View Lorry Controller Status