- 16 Jan, 2013 1 commit
-
-
Elena Stepanova authored
-
- 14 Jan, 2013 1 commit
-
-
unknown authored
-
- 13 Jan, 2013 3 commits
-
-
Elena Stepanova authored
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)
-
Igor Babaev authored
-
Igor Babaev authored
The bug could cause a crash when several connections needed persistent statistics for the same table. Also added a missing call of set_statistics_for_table() in the code of the function mysql_update.
-
- 11 Jan, 2013 2 commits
- 10 Jan, 2013 5 commits
-
-
unknown authored
-
Sergey Petrunya authored
Backport the fix from 10.0 tree - The problem was that thd_killed() may be called by innodb from an internal innodb thread. - Fixed by not processing APC requests when we're not in the thread that owns the APC target.
-
unknown authored
-
unknown authored
-
unknown authored
-
- 09 Jan, 2013 7 commits
- 08 Jan, 2013 2 commits
-
-
Igor Babaev authored
-
Igor Babaev authored
Made allocation of memory for statistical data in a table share to be thread safe. This memory is now allocated in a special MEM_ROOT that is created for each table share.
-
- 05 Jan, 2013 1 commit
-
-
Vladislav Vaintroub authored
Remove timed mutexes in XtraDB - obsolete feature that does not link on Windows, if plugin is build dynamically It was already removed from innobase in the past.
-
- 01 Jan, 2013 1 commit
-
-
Vladislav Vaintroub authored
-
- 30 Dec, 2012 1 commit
-
-
Elena Stepanova authored
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
-
- 28 Dec, 2012 1 commit
-
-
Elena Stepanova authored
storage_engine tests and upstream engines/* suites went out of sync with 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)
-
- 24 Dec, 2012 1 commit
-
-
Sergey Petrunya authored
- update ha_cassandra::start_bulk_insert() definition to match those in class handler.
-
- 23 Dec, 2012 3 commits
- 20 Dec, 2012 6 commits
-
-
Igor Babaev authored
-
Igor Babaev authored
The patch lifts the limitation of the current implementation of ALTER TABLE that does not allow to build unique/primary indexes by sort for MyISAM and Aria engines.
-
Sergey Petrunya authored
- Cleanup ha_cassandra::store_lock() - Remove dummy ha_cassandra::delete_table() - Add HA_TABLE_SCAN_ON_INDEX to table_flags()
-
Sergey Petrunya authored
- Register counters directly in the array passed to maria_declare_plugin. As a consequence, FLUSH TABLES will reset the counters. - Update test results accordingly.
-
Sergey Petrunya authored
- Partially address review feedback. - Update cassandra.test result result - make cassandra.test timezone-agnostic
-
Igor Babaev authored
-
- 18 Dec, 2012 2 commits
-
-
unknown authored
Implement it in a different way that works on both release and debug builds, and still uses --skip instead of --require.
-
Sergei Golubchik authored
have_openssl variable was ON even when OpenSSL was not used (but YaSSL was). fix that, so that have_openssl really corresponds to OpenSSL rename not_openssl.inc to not_ssl.inc and fix the test accordingly.
-
- 17 Dec, 2012 3 commits
-
-
Sergei Golubchik authored
remove unused require files
-
Sergei Golubchik authored
MDEV-438 Microseconds: Precision is ignored in CURRENT_TIMESTAMP(N) when it is given as a default column value For MySQL 5.6 compatibility, support precision specification in CURRENT_TIMESTAMP in a default clause, when it's not less than the column's precision.
-
Sergei Golubchik authored
-