summaryrefslogtreecommitdiff
path: root/mysql-test/suite/engines
Commit message (Collapse)AuthorAgeFilesLines
* MDEV-7635: Update tests to adapt to the new default sql_modeNirbhay Choubey2017-02-1046-2313/+2351
|
* Follow-up for a411d7f4f6 - change in formatting of SHOW CREATE TABLEElena Stepanova2016-12-1528-393/+393
|
* Follow-up for 180065ebb0 - removal of redundant parenthesesElena Stepanova2016-12-151-24/+24
|
* cleanup: remove Item::intro_versionSergei Golubchik2016-12-1218-724/+724
| | | | | and partition_info::set_show_version_string - they were already broken and impossible to maintain
* Follow-up for big error-message cleanup (trailing dots were removed)Elena Stepanova2016-10-132-28/+28
|
* MDEV-10877 xxx_unicode_nopad_ci collationsAlexander Barkov2016-09-232-0/+20
|
* Merge branch '10.2' into bb-10.2-janSergei Golubchik2016-09-198-1976/+2132
|\
| * MDEV-10758 engines/funcs.db_alter_collate_ascii and ↵Alexander Barkov2016-09-072-0/+156
| | | | | | | | engines/funcs.db_alter_collate_utf8 fail with wrong results
| * clarify the error message for frm size overflowSergei Golubchik2016-08-271-2/+2
| |
| * do not quote numbers in the DEFAULT clause in SHOW CREATESergei Golubchik2016-08-275-1974/+1974
| |
* | Fix test failure on tc_partition_list_directory becauseJan Lindström2016-09-141-0/+1
|/ | | | | | innodb-strict-mode by default is now ON, disabling it for this test because test uses INDEX DICECTORY that is not really supported by InnoDB.
* clarify ER_CANT_DROP_FIELD_OR_KEYSergei Golubchik2016-07-021-1/+1
| | | | include the dropped object type
* Post-commit test fixesElena Stepanova2016-07-0220-2419/+2418
| | | | | | | - 12d75e6121 - new thread stack size - 99e48cb1d9 - warning text changed - 6c173324ff - default values for BLOBs - c87e002bbb - don't return a negative zero
* Merge branch '10.1' into 10.2Sergei Golubchik2016-06-302-0/+10
|\
| * Adding collationsmasterAlexander Barkov2016-05-302-0/+8
| | | | | | | | utf8mb4_thai_520_w2, ucs2_thai_520_w2, utf16_thai_520_w2, utf32_thai_520_w2
| * Clean-ups for MDEV-10132 utf8_thai_520_w2 collation:Alexander Barkov2016-05-262-0/+2
| | | | | | | | | | - Changing strnxfrm_multiply from 8 to 4, as agreed with Pruet Boonma - Adjusting tests
* | Follow-up #2 for MDEV-6720 (enable connection log in mysqltest by default)Elena Stepanova2016-06-261-0/+7
| | | | | | | | Result file in engines/funcs test suite needs to be updated accordingly
* | General spell fixing in comments and stringsOtto Kekäläinen2016-06-081-1/+1
|/
* Fixed engine test results in accordance with changes made in scope ofElena Stepanova2015-11-064-7/+33
| | | | commit 6b20342651bb5207b6c125d2d11b664a1bebcc41
* --getopt-prefix-matching command-line optionSergei Golubchik2015-02-101-1/+1
|
* Merge branch '10.0' into merge-wipSergei Golubchik2015-01-3125-809/+167
|\
| * Run engines tests for MyISAM and in-built InnoDBElena Stepanova2014-12-052-0/+19
| |
| * MDEV-7255 Failures in engines/* tests, part 6Elena Stepanova2014-12-041-6/+6
| | | | | | | | | | Updated hardcoded event numbers according to current GTID logic
| * MDEV-7255 Failures in engines/* tests, part 5Elena Stepanova2014-12-042-2/+2
| | | | | | | | | | RENAME TABLE on a non-existing table produces a better error message
| * MDEV-7255 Failures in engines/* tests, part 4Elena Stepanova2014-12-044-110/+110
| | | | | | | | | | | | Updated engines/* test results according to the bugfix MDEV-5894 (MySQL BUG#34750: Print database name in Unknown Table error message)
| * MDEV-7255 Failures in engines/* tests, part 3Elena Stepanova2014-12-042-11/+11
| | | | | | | | | | Error message was changed along with CREATE OR REPLACE TABLE fixes
| * MDEV-7255 Failures in engines/* tests, part 2Elena Stepanova2014-12-044-671/+0
| | | | | | | | | | | | Result files updated according to bugfix for MySQL#55843 (Handled condition appears as not handled)
| * MDEV-7255 Failures in engines/* tests, part 1Elena Stepanova2014-12-0310-9/+19
| | | | | | | | | | | | | | In 10.0 output of SHOW DATABASES appears to be sorted, while in result files it is not. Added sorted_result for certainty and updated result files.
* | Merge 10.0.14 into 10.1Sergei Golubchik2014-10-153-19/+17
|\ \ | |/
| * Don't give warning if there are two unique keys used with INSERT .. ON ↵Michael Widenius2014-09-161-17/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | DUPLICATE KEY UPDATE. We should assume that the store engine will report the first duplicate key for this case. Old code of suppression of unsafe logging error with LIMIT didn't work, because of wrong usage of my_interval_timer(). Suppress unsafe logging errors to the error log if we get too many unsafe logging errors in a short time. This is to not overflow the error log with meaningless errors. - Each error code is suppressed and counted separately. - We do a 5 minute suppression of new errors if we get more than 10 errors in that time. Only print unsafe logging errors if log_warnings > 1. mysql-test/suite/binlog/r/binlog_stm_unsafe_warning.result: Update test results as INSERT ... ON DUPLICATE KEY UPDATE doesn't get logged anymore mysql-test/suite/binlog/r/binlog_unsafe.result: Update test results as INSERT ... ON DUPLICATE KEY UPDATE doesn't get logged anymore mysql-test/suite/engines/README: Fixed typos mysql-test/suite/rpl/r/rpl_known_bugs_detection.result: Update test results as INSERT ... ON DUPLICATE KEY UPDATE doesn't get logged anymore sql/sql_base.cc: Don't log warning if there are two unique keys used with INSERT .. ON DUPLICATE KEY UPDATE. We should assume that the store engine will report the first duplicate key for this case. sql/sql_class.cc: Suppress error in binary log if we get too many unsafe logging errors in a short time. Only print unsafe logging errors if log_warnings > 1
| * 5.5.39 mergeSergei Golubchik2014-08-072-2/+4
| |\
| | * MDEV-6378 mtr engines iuds time tests failElena Stepanova2014-07-282-2/+4
| | | | | | | | | | | | | | | | | | | | | | | | - adjusted a test result according to the change made for MDEV-6100; - added explicit timezone for engines/iuds, since MTR in MariaDB does not set it like MySQL's, and tests with constant TIMESTAMP can have different outcome
* | | MDEV-34 delete storage/ndb and sql/*ndb* (and collateral changes)Sergei Golubchik2014-10-1115-156/+1
|/ / | | | | | | | | | | | | | | | | | | remove: * NDB from everywhere * IM from mtr-v1 * packaging/rpm-oel and packaging/rpm-uln * few unused spec files * plug.in file * .bzrignore
* | MDEV-4929 Myanmar collationAlexander Barkov2013-12-202-0/+10
| |
* | Merging xxx_unicode_520_ci and xxx_vietnamese_ci from MySQL-5.6.Alexander Barkov2013-11-123-0/+21
| |
* | MDEV-5241: Collation incompatibilities with MySQL-5.6Michael Widenius2013-11-092-10/+20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - Character set code & tests from Alexander Barkov - Integration with ALTER TABLE, REPAIR and open_table from Monty The problem was that MySQL 5.6 added some croatian and vitanamese character set collations that are incompatible with MariaDB. The fix is to move the MariaDB conflicting collation numbers out of the region that MySQL is likely to use. mysql_upgrade, REPAIR TABLE or ALTER TABLE will fix the collations. If one tries to access and old incompatible table, one will get the error "Table upgrade required...." After this patch, MariaDB supports all the MySQL character set collations and the old MariaDB croatian collations, which are closer to the latest standard than the MySQL versions. New character sets: ucs2_croatian_mysql561_uca_ci utf8_croatian_mysql561_uca_ci utf16_croatian_mysql561_uca_ci utf32_croatian_mysql561_uca_ci utf8mb4_croatian_mysql561_uca_ci Other things: - Fixed some compiler warnings - mysql_upgrade prints information about repaired tables. - Increased version number VERSION: Increased VERSION number client/mysqlcheck.c: Print repaired table name when using --verbose include/m_ctype.h: Add new MariaDB collation regions that are not likely to conflict with MySQL include/my_base.h: Added flag to detect if table was opened for ALTER TABLE mysql-test/r/ctype_ldml.result: Updated result mysql-test/r/ctype_uca.result: Updated result mysql-test/r/ctype_upgrade.result: Updated result mysql-test/r/ctype_utf16_uca.result: Updated result mysql-test/r/ctype_utf32_uca.result: Updated result mysql-test/r/ctype_utf8mb4_uca.result: Updated result mysql-test/std_data/ctype_upgrade: Test files for testing upgrading of conflicting collations mysql-test/suite/engines/funcs/r/db_alter_collate_ascii.result: New collations added mysql-test/suite/engines/funcs/r/db_alter_collate_utf8.result: New collations added mysql-test/suite/innodb/r/innodb_ctype_ldml.result: Updated test result mysql-test/suite/innodb/t/innodb_ctype_ldml.test: Updated test result mysql-test/suite/plugins/r/show_all_plugins.result: Updated version number mysql-test/suite/roles/create_and_drop_role_invalid_user_table.result: Updated version number mysql-test/t/ctype_ldml.test: Updated test mysql-test/t/ctype_uca.test: Testing of new collations mysql-test/t/ctype_upgrade.test: Testing of upgrading tables with old collations The test ensures that: - We will get an error if we try to open a table with old collations. - CHECK TABLE will detect that the table needs to be upgraded. - ALTER TABLE and REPAIR will fix the table. - mysql_upgrade works as expected mysql-test/t/ctype_utf16_uca.test: Testing of new collations mysql-test/t/ctype_utf32_uca.test: Testing of new collations mysql-test/t/ctype_utf8mb4_uca.test: Testing of new collations mysys/charset-def.c: Added new character sets mysys/charset.c: Always give an error, if requested, if a character set didn't exist sql/handler.cc: - Added upgrade_collation() to check if collation is compatible with old version - check_collation_compatibility() checks if we are using an old collation from MariaDB 5.5 or MySQL 5.6 - ha_check_for_upgrade() returns HA_ADMIN_NEEDS_ALTER if we have an incompatible collation sql/handler.h: Added new prototypes sql/sql_table.cc: - Mark that tables are opened for ALTER TABLE - If table needs to be upgraded, ensure we are not using online alter table. sql/table.cc: - If we are using an old incompatible collation, change to use the new one and mark table as incompatible. - Give an error if we try to open an incompatible table. sql/table.h: Added error that table needs to be rebuild storage/connect/ha_connect.cc: Fixed compiler warning strings/ctype-uca.c: New character sets
* | Recording correct test results:Alexander Barkov2013-11-062-0/+14
| | | | | | | | | | | | mysql-test/suite/engines/funcs/r/db_alter_collate_ascii.result mysql-test/suite/engines/funcs/r/db_alter_collate_utf8.result
* | 5.5 merge and fixes for compiler/test errorsSergei Golubchik2013-09-182-10/+0
|\ \ | |/
| * remove PBXTSergei Golubchik2013-08-302-10/+0
| |
* | 5.5 mergeSergei Golubchik2013-03-273-270/+152
|\ \ | |/
| * merge with mysql-5.5.30 minus few incorrect or not applicable changesetsSergei Golubchik2013-02-283-270/+152
| |\
| | * BUG#12359942 - REPLICATION TEST FROM ENGINE SUITE RPL_ROW_UNTIL TIMES OUTShivji Kumar Jha2012-12-091-2/+1
| | |\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | patch to fix post push falures in pb2 bzr merge 5.1->5.5 BUG#15872504 - REMOVE MYSQL-TEST/INCLUDE/GET_BINLOG_DUMP_THREAD_ID.INC bzr merge 5.1->5.6
| | * \ BUG#12359942 - REPLICATION TEST FROM ENGINE SUITE RPL_ROW_UNTIL TIMES OUTShivji Kumar Jha2012-12-053-270/+153
| | |\ \ | | | |/ | | | | | | | | bzr merge 5.1->5.5
| | | * BUG#12359942 - REPLICATION TEST FROM ENGINE SUITE RPL_ROW_UNTIL TIMES OUTShivji Kumar Jha2012-11-303-261/+152
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | === Problem === The test is dependent on binlog positions and checks to see if the command 'START SLAVE' functions correctly with the 'UNTIL' clause added to it. The 'UNTIL' clause is added to specify that the slave should start and run until the SQL thread reaches a given point in the master binary log or in the slave relay log. The test uses hard coded values for MASTER_LOG_POS and RELAY_LOG_POS, instead of extracting it using query_get_value() function. There is a test 'rpl.rpl_row_until' which does the similar thing but uses query_get_value() function to set the values of MASTER_LOG_POS/ RELAY_LOG_POS. To be precise, rpl.rpl_row_until is a modified version of engines/func.rpl_row_until.test. The use of hard coded values may lead the slave to stop at a position which may differ from the expected position in the binlog file, an example being the failure of engines/funcs.rpl_row_until in mysql-5.1 given as: "query 'select * from t2' failed. Table 'test.t2' doesn't exist". In this case, the slave actually ran a couple of extra commands as a result of which the slave first deleted the table and then ran a select query on table, leading to the above mentioned failure. === Fix === 1) Fixed the code for failure seen in rpl.rpl_row_until. This test was also failing although the symptoms of failure were different. 2) Copied the contents from rpl.rpl_row_until into into engines/funcs.rpl.rpl_row_until. 3) Updated engines/funcs.rpl_row_until.result accordingly. mysql-test/suite/engines/funcs/r/rpl_row_until.result: modified to accomodate the changes in corresponding test file. mysql-test/suite/engines/funcs/t/disabled.def: removed from the list of disabled tests. mysql-test/suite/engines/funcs/t/rpl_row_until.test: fixed rpl.rpl_row_until and copied its content to engines/funcs.rpl_row_until. The reason being both are same tests but rpl.rpl_row_until is an updated version. mysql-test/suite/rpl/t/disabled.def: removed from the list of disabled tests. sql/sql_repl.cc: Added a check to catch an improper combination of arguements passed to 'START SLAVE UNTIL'. Earlier, START SLAVE UNTIL MASTER_LOG_FILE='master-bin.000001', MASTER_LOG_POS=561, RELAY_LOG_POS=12; passed. It is now detected and an error is reported.
* | | | MDEV-3990: engine tests went out of sync with current MariaDB codeElena Stepanova2013-01-132-8/+1
|/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Reasons: alter_tablespace.rdiff: tc_rename_error.result: from monty@askmonty.org-20120529213755-876ptdhhaj0t7l8r (Added text for errno in error messages) insert_time.result: from sergii@pisem.net-20120908101555-37w00eyfrd9noc06 (MDEV-457 - Inconsistent data truncation) misc.result: from igor@askmonty.org-20130109033433-5awdv0w6vbpigltw (MDEV-3806/mwl248 - Engine independent statistics) tbl_opt_row_format.rdiff: from monty@askmonty.org-20120706161018-y5teinbuqpchle2m (Fixed wrong error codes) vcol.rdiff: sergii@pisem.net-20121217100039-ikj1820nrku7p6d5 (simplify the handler api)
* | | storage_engine tests and upstream engines/* suites went out of sync with ↵Elena Stepanova2012-12-2820-1400/+1985
| | | | | | | | | | | | | | | | | | | | | | | | | | | current MariaDB code. Reasons: - as of 5.5.27, YEAR(2) is deprecated, hence the new warning; - MDEV-553 - different error code/message on out-of-range autoincrement; - INSERT IGNORE now produces a warning if a duplicate was encountered (change pushed along with MDEV-553)
* | | merge with MySQL 5.5.27Sergei Golubchik2012-08-093-0/+24
|\ \ \ | |/ / | | | | | | manually checked every change, reverted incorrect or stupid changes.
| * | manual merge (WL6219)Gleb Shchepa2012-06-293-0/+24
| |\ \ | | |/ | | | | | | | | | sql/sql_yacc.yy: manual merge (backport of WL6219)
| | * Backport of the deprecation warning from WL#6219: "Deprecate and remove ↵Gleb Shchepa2012-06-293-0/+24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | YEAR(2) type" Print the warning(note): YEAR(x) is deprecated and will be removed in a future release. Please use YEAR(4) instead on "CREATE TABLE ... YEAR(x)" or "ALTER TABLE MODIFY ... YEAR(x)", where x != 4
* | | MDEV-369: Mismatches in MySQL engines test suiteElena Stepanova2012-08-023-7/+7
| | | | | | | | | | | | | | | Post-merge fixes for mismatches that only affect 5.5 (but not 5.3)
View Lorry Controller Status