- 02 Feb, 2015 5 commits
-
-
Monty authored
-
Sergei Golubchik authored
* error reporting was never needed * avoid useless transformaton hton to db_type to hton * in many cases the engine was guaranteed to exist, add asserts * use ha_default_handlerton() instead of ha_checktype(DB_TYPE_DEFAULT)
-
Sergei Golubchik authored
but keep the code cleanup. as it turns out, it didn't change the behavior, which is good :)
-
Sergei Golubchik authored
-
Sergei Golubchik authored
-
- 01 Feb, 2015 5 commits
-
-
Monty authored
Now this works the same way as all other multi source variables.
-
Monty authored
Extend interface for 'show variables' with current scope
-
Monty authored
-
Monty authored
-
Sergei Golubchik authored
-
- 31 Jan, 2015 7 commits
-
-
Sergei Golubchik authored
in case args[0] changes between PREPARE and EXECUTE
-
Sergei Golubchik authored
in particular, not the one that destructively changes Item's charset (meaning different metadata for PREPARE and EXECUTE)
-
Sergei Golubchik authored
-
Sergei Golubchik authored
-
Sergei Golubchik authored
-
Sergei Golubchik authored
* fix the test to pass * rearrange tests in a file to allow it to auto-merge in the future
-
Sergei Golubchik authored
-
- 30 Jan, 2015 2 commits
-
-
Sergei Golubchik authored
-
Sergei Golubchik authored
use the old registry branch, even if we changed the "manufacturer" string
-
- 29 Jan, 2015 6 commits
-
-
Oleksandr Byelkin authored
MDEV-7024: Assertion `! is_set()' failed in Diagnostics_area::set_eof_status on executing ANALYZE SELECT via PS select_send::is_result_interceptor() should return FALSE because it return results to the client.
-
Sergei Golubchik authored
-
Sergei Golubchik authored
-
Sergei Golubchik authored
added a script to regenerate certificates easily in the future (2035!) restored server8k-key.pem to actually be 8K key, as it was supposed to
-
Oleksandr Byelkin authored
MDEV-7023: Error 2027: Malformed packet and assertion `field_types == 0 || field_types[field_pos] == MYSQL_TYPE_INT24 || field_types[field_pos] == MYSQL_TYPE_LONG' failure in Protocol_text::store_long The problem was that sp_head::MULTI_RESULTS was not set correctly for ANALYZE statement.
-
Sergei Golubchik authored
-
- 28 Jan, 2015 1 commit
-
-
unknown authored
Backport from mysql 5.7. The patch reviewed, test added.
-
- 27 Jan, 2015 1 commit
-
-
Jan Lindström authored
-
- 25 Jan, 2015 1 commit
-
-
Sergey Petrunya authored
Merged revision 5224 from mysql-5.6 and added a test case. .. revno: 5224 committer: Sergey Glukhov <sergey.glukhov@oracle.com> branch nick: mysql-5.6 timestamp: Wed 2013-06-19 14:24:08 +0400 message: Bug#16620047 INCORRECT QUERY RESULT (AFTER SERVER UPGRADE)
-
- 24 Jan, 2015 1 commit
-
-
Sergei Golubchik authored
-
- 29 Jan, 2015 2 commits
-
-
Michael Widenius authored
-
Michael Widenius authored
MDEV-6668: Server crashes in check_view_single_update on concurrent DDL/DML flow with views and triggers Call mysql_derived_reinit() if we are reusing view. This is needed as during a previous error condition the view may not have been reset sql/sql_derived.cc: More DBUG_PRINT Always reset merged_for_insert (no reason to not do that) sql/sql_derived.h: Added prototype sql/sql_insert.cc: More DBUG_PRINT Added DBUG_ASSERT sql/sql_view.cc: Call mysql_derived_reinit() if we are reusing view. This is needed as during a previous error condition the view may not have been reset sql/table.cc: More DBUG_PRINT
-
- 23 Jan, 2015 4 commits
-
-
Sergei Golubchik authored
-
Kristian Nielsen authored
After fix of MDEV-6728, the KILL signal is reset at the start of query execution. This means that in this test case, we need to wait for the to-be-killed query to have started; otherwise the kill signal can be lost, causing the test case to fail.
-
Sergei Golubchik authored
-
Sergei Golubchik authored
-
- 22 Jan, 2015 3 commits
-
-
Nirbhay Choubey authored
Added a SESSION-only system variable "wsrep_dirty_reads" to allow SELECT queries to pass even when the node is not prepared to accept queries (wsrep_ready=OFF). Added a test case.
-
Kristian Nielsen authored
The test case deliberately crashes the server. If this crash happens in the middle of a page write, InnoDB crash recovery recovers the page from the doublewrite buffer, writing a message to the error log that is flagged as a test failure by mysql-test-run. So add a suppression for this.
-
Sergei Golubchik authored
-
- 21 Jan, 2015 2 commits
-
-
Sergei Golubchik authored
-
Sergei Golubchik authored
-