summaryrefslogtreecommitdiff
path: root/mysql-test
Commit message (Collapse)AuthorAgeFilesLines
* Fixed MySQL bug #69861 LAST_INSERT_ID is replicated incorrectly if ↵Michael Widenius2013-08-273-0/+68
| | | | | | | | | | | | | | | | | | replication filters are used mysql-test/suite/rpl/r/last_insert_id.result: Test case for last_insert_id mysql-test/suite/rpl/t/last_insert_id.cnf: Test case for last_insert_id mysql-test/suite/rpl/t/last_insert_id.test: Test case for last_insert_id sql/log_event.cc: Added DBUG_PRINT Set thd->first_successful_insert_id_in_prev_stmt_for_binlog when setting thd->first_successful_insert_id_in_prev_stmt. This is required to get last_insert_id() replicated. This is analog to how read_first_successful_insert_id_in_prev_stmt() works. sql/rpl_utility.cc: Added DBUG_PRINT
* Merge fix for MDEV-4942, 5.3->5.5Sergey Petrunya2013-08-263-0/+40
|\
| * Fixed bug mdev-4942.Igor Babaev2013-08-233-0/+40
| | | | | | | | | | Made sure that degenerate conjunctions/disjunctions are obtained from AND/OR conditions.
* | MergeIgor Babaev2013-08-235-3/+48
|\ \
| * | Fixed bug mdev-4420.Igor Babaev2013-08-235-3/+48
| | | | | | | | | | | | | | | | | | | | | | | | The code of JOIN::optimize that performed substitutions for the best equal field in all ref items did not take into account that a multiple equality could contain the result of the single-value subquery if the subquery is inexpensive. This code was corrected. Also made necessary corresponding corrections in the code of make_join_select().
* | | Merging from 5.3Alexander Barkov2013-08-222-0/+60
|\ \ \ | | |/ | |/| | | | | | | | | | pending merges: Alexander Barkov 2013-08-22 MDEV-4804 Date comparing false result
| * | MDEV-4804 Date comparing false resultAlexander Barkov2013-08-222-0/+60
| | |
* | | Automatic mergeSergey Petrunya2013-08-222-0/+37
|\ \ \ | |_|/ |/| |
| * | MDEV-4840: Wrong result (missing rows) on LEFT JOIN with InnoDB tablesSergey Petrunya2013-08-222-0/+37
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fix two problems in table elimination code: - Before marking a "value" as bound, check if it is already bound. Marking the same value as bound twice could confuse a module that depends on this value, because Dep_module_XXX use counters to know when they become bound. - When checking whether field is part of a key, ignore "extended keys" property.
* | | MergeIgor Babaev2013-08-213-0/+46
|\ \ \ | | |/ | |/|
| * | MDEV-4908: Assertion `((Item_cond *) cond)->functype() == ((Item_cond *) ↵unknown2013-08-213-0/+46
| | | | | | | | | | | | | | | | | | new_item)->functype()' fails on a query with IN and equal conditions, AND/OR, materialization+semijoin A new AND Item should be prepared (fix_field() call) before using.
* | | Merge 5.3->5.5Igor Babaev2013-08-212-0/+58
|\ \ \ | |/ / | | / | |/ |/|
| * Fixed a bug/typo in the patch for mdev-4355, noticed after the patchIgor Babaev2013-08-201-3/+3
| | | | | | | | | | | | had been merged into 5.5. Corrected the result of the output from the test case for mdev 4895.
| * Fix bug MDEV-4895 Valgrind warnings (Conditional jump or move depends on ↵unknown2013-08-202-0/+58
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | uninitialised value) in Field_datetime::get_date on GREATEST(..) IS NULL Analysis: The cause of the valgrind warning was an attempt to evaluate a Field that was not yet read. The reason was that on one hand Item_func_isnotnull was marked as constant by Item_func_isnotnull::update_used_tables, and this allowed eval_const_cond() to be called. On the other hand Item_func_isnotnull::val_int() evaluated its argument as if it was not constant. Solution: The fix make sure that Item_func_isnotnull::val_int() doesn't evaluate its argument when it is constant and cannot be NULL, because the result is known in this case.
* | Backport from 10.0-base fix for tests failing when vardir has no execute ↵unknown2013-08-201-3/+1
| | | | | | | | permissions.
* | Merge 5.3->5.5.Igor Babaev2013-08-1820-26/+420
|\ \ | |/ | | | | | | | | | | In particular: Merged the patch for bug mdev-4418 from 5.3 into 5.5. Fixed a bug in the patch that should be backported to 5.3.
| * Fixed bug mdev-4418.Igor Babaev2013-08-1613-10/+81
| | | | | | | | | | | | After single row substitutions there might appear new equalities. They should be properly propagated to all AND/OR levels the WHERE condition. It's done now with an additional call of remove_eq_conds().
| * MergeIgor Babaev2013-08-155-5/+185
| |\
| | * Fixed bug mdev-4355.Igor Babaev2013-08-155-5/+185
| | | | | | | | | | | | | | | | | | | | | | | | This patch almost totally revised the patch for bug mdev-4177. The latter had too many defects. In particular, it did not propagate multiple equalities formed when merging a degenerate disjunct into underlying AND formula.
| * | Merge 5.2->5.3Igor Babaev2013-08-155-6/+149
| |\ \
| | * \ Merge 5.1->5.2Igor Babaev2013-08-142-4/+78
| | |\ \
| | | * | Fixed bug mdev-4894.Igor Babaev2013-08-132-4/+78
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This a an old legacy performance bug. When a very selective range scan existed for the second table in a join, and, at the same time, there was another range condition depending on the fields of the first table, the optimizer chose a plan with 'Range checked for each record'. This plan was extremely inefficient in comparison with the regular selective range scan. As a matter of fact the range scan chosen for each record was the same as that selective range scan. Changed the test case for bug 24776 to preserve the old output for explain.
| | * | | MDEV-4823: Server crashes in Item_func_not::fix_fields on creating a table ↵unknown2013-08-012-0/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | with a virtual column using NOT fix_field() call protocol was brocken (zero pointer passed as link to item which is possible only if you are sure that there can not be Items which transforms).
* | | | | Merge from 5.3Alexander Barkov2013-08-124-0/+59
|\ \ \ \ \ | |/ / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | modified: mysql-test/r/dyncol.result mysql-test/r/type_time.result mysql-test/t/dyncol.test mysql-test/t/type_time.test mysys/ma_dyncol.c sql/item.cc sql/item_func.cc pending merges: Alexander Barkov 2013-08-12 MDEV-4652 Wrong result for CONCAT(GREATEST(T... sanja@montyprogr... 2013-08-01 MDEV-4811 Assertion `offset < 0x1f' f...
| * | | | MDEV-4652 Wrong result for CONCAT(GREATEST(TIME('00:00:01'),TIME('00:00:00'))Alexander Barkov2013-08-122-0/+15
| | | | |
| * | | | MDEV-4811 Assertion `offset < 0x1f' fails in type_and_offset_store on COLUMN_ADDunknown2013-08-012-0/+44
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | MDEV-4812 Valgrind warnings (Invalid write) in dynamic_column_update_many on COLUMN_ADD Fixed problem of working on wrong data (do not allow offset to out of string length).
* | | | | mysql --skip-column-names flag should not affect alignment of field values,Sergei Golubchik2013-08-082-0/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | set num_flag[] unconditionally, not under "if (column_names)" http://ronaldbradford.com/blog/unexplained-trivial-mysql-behavior-2013-08-02/
* | | | | Merge from 5.3Alexander Barkov2013-08-082-0/+35
|\ \ \ \ \ | |/ / / / | | | | | | | | | | | | | | | | | | | | pending merges: Alexander Barkov 2013-08-08 MDEV-4653 Wrong result for CONVERT_TZ(TIME('...
| * | | | MDEV-4653 Wrong result for CONVERT_TZ(TIME('00:00:00'),'+00:00','+7:5')Alexander Barkov2013-08-082-0/+35
| | | | |
* | | | | Merge from 5.3Alexander Barkov2013-08-082-0/+36
|\ \ \ \ \ | |/ / / / | | | | | | | | | | | | | | | | | | | | pending merges: Alexander Barkov 2013-08-08 MDEV-4512 Valgrind warnings in my_long10_to_...
| * | | | MDEV-4512 Valgrind warnings in my_long10_to_str_8bit on INTERVAL and ↵Alexander Barkov2013-08-082-0/+37
| | |_|/ | |/| | | | | | | | | | | | | | | | | | | | | | DATE_ADD with incorrect types Fixing a typo: bit AND (&) was erroneously used instead of logical AND (&&)
* | | | Automatic mergeSergey Petrunya2013-08-051-2/+2
|\ \ \ \
| * | | | Update test results after fix for MDEV-4687Sergey Petrunya2013-08-051-2/+2
| | | | |
* | | | | The test was non-deterministic while choosing an alternative storageElena Stepanova2013-08-051-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | engine
* | | | | Deliberate change in behavior introduced along with the fix for MDEV-4310Elena Stepanova2013-08-052-36/+36
|/ / / /
* | | | MDEV-4817: Optimizer fails to optimize expression of the form 'FOO' IS NULLSergey Petrunya2013-07-319-3/+71
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - Modify the way Item_cond::fix_fields() and Item_cond::eval_not_null_tables() calculate bitmap for Item_cond_or::not_null_tables(): if they see a "... OR inexpensive_const_false_item OR ..." then the item can be ignored. - Updated test results. There can be more warnings produced since parts of WHERE are evaluated more times.
* | | | Fix for MDEV-4219 A simple select query returns random data (upstream bug#68473)unknown2013-07-172-0/+89
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In the case of loose scan used as input for order by, end_send() didn't detect correctly that a loose scan was used, and didn't copy the non-aggregated fields from the temp table used for ORDER BY. The fix uses the fact that the quick select used for sorting is attached to JOIN::pre_sort_join_tab instead of JOIN::join_tab.
* | | | mysql-5.5.32 mergeSergei Golubchik2013-07-1627-51/+129
|\ \ \ \
| * | | | Bug #16632543 - INCORRECT VALUE OF BOGOMIPS IN MYSQLTESTsayantan dutta2013-04-161-2/+2
| | | | |
| * | | | BUG#16615117 MYSQLDUMP PRODUCES A CHANGE MASTER STATEMENTVenkatesh Duggirala2013-04-121-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | WITH A PORT NUMBER ENCLOSED IN QUOTES Problem: mysqldump --dump-slave --include-master-host-port prints the CHANGE MASTER command in the generated logical backup. The PORT number that is generated with this command is a string and should be an integer. Fix: Remove the Enclosed quotes for port number.
| * | | | Bug #16401597 - MTR V1 RETURNS INCORRECT PATH TO VARIABLE @@BASEDIRsayantan dutta2013-04-041-7/+4
| | | | |
| * | | | Bug#11765629 CMAKE: CAN SUPPRESS INSTALLATION OF SQL-BENCH, BUT NOT MYSQL-TESTTor Didriksen2013-04-021-4/+16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Don't try to install anything into INSTALL_MYSQLTESTDIR if it is explicitly set empty on the cmake command line.
| * | | | Bug#15948818-SEMI-SYNC ENABLED MASTER CRASHES WHEN EVENTVenkatesh Duggirala2013-03-292-0/+63
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | SCHEDULER DROPS EVENTS Problem: On a semi sync enabled server (Master/Slave), if event scheduler drops an event after completion, server crashes. Analaysis: If an event is created with "ON COMPLETION NOT PRESERVE" clause, event scheduler deletes the event upon event completion(expiration) and the thread object will be destroyed. In the destructor of the thread object, mysys_var member is set to zero explicitly. Later from the same destructor call(same execution path), incase of semi sync enabled server, while cleanup is called, THD::mysys_var member is accessed by THD::enter_cond() function which causes server to crash. Fix: mysys_var should not be explicitly set to zero and also it is not required. sql/sql_class.cc: mysys_var should not be explicitly set to zero.
| * | | | Bug #16403186 - MTR ON WINDOWS SHOULD NOT TRY TO START CDB IF RUNNING WITH ↵sayantan dutta2013-03-282-5/+9
| | | | | | | | | | | | | | | | | | | | PARALLEL
| * | | | Merge from mysql-5.1 to mysql-5.5Sujatha Sivakumar2013-03-272-2/+2
| |\ \ \ \
| | * | | | Bug#11829838: ALTER TABLE NOT BINLOGGED WITHSujatha Sivakumar2013-03-272-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | --BINLOG-IGNORE-DB AND FULLY QUALIFIED TABLE Problem: ======= An ALTER TABLE statement is not written to binlog if server started with "--binlog-ignore-db some database" and 'fully qualified' table names are used in the ALTER TABLE statement altering table different from current database context. Analysis: ======== The above mentioned problem not only affects "ALTER TABLE" statements but also to all kind of statements. Once the current default database becomes "NULL" none of the statements will be binlogged. The current behaviour is such that if the user has specified restrictions on which database needs to be replicated and the default db is not specified, then do not replicate. This means that "NULL" is considered to be equivalent to everything (default db = null implied ignore don't log the statement). Fix: === "NULL" should not be considered as equivalent to everything. Since the filtering criteria is not equal to "NULL" the statement should be logged into binlog. mysql-test/suite/rpl/r/rpl_loaddata_m.result: Earlier when defalut database was "NULL" DROP TABLE was not getting logged. Post this fix it will be logged and the DROP will fail at slave as the table creation was skipped by master as --binlog-ignore-db=test. mysql-test/suite/rpl/t/rpl_loaddata_m.test: Earlier when defalut database was "NULL" DROP TABLE was not getting logged. Post this fix it will be logged and the DROP will fail at slave as the table creation was skipped by master as --binlog-ignore-db=test. sql/rpl_filter.cc: Replaced DBUG_RETURN(0) with DBUG_RETURN(1).
| * | | | | local merge.Nirbhay Choubey2013-03-222-6/+6
| |\ \ \ \ \ | | |/ / / /
| | * | | | Bug#12671635 : Updating embedded tests.Nirbhay Choubey2013-03-222-6/+6
| | | | | |
| * | | | | local merge.Nirbhay Choubey2013-03-222-5/+5
| |\ \ \ \ \ | | |/ / / /
| | * | | | Bug#12671635 : Fixing test cases.Nirbhay Choubey2013-03-222-5/+5
| | | | | |
View Lorry Controller Status