- 20 Nov, 2012 2 commits
- 19 Nov, 2012 1 commit
-
-
Sergei Golubchik authored
-
- 17 Nov, 2012 1 commit
-
-
Sergei Golubchik authored
-
- 12 Nov, 2012 1 commit
-
-
Sergei Golubchik authored
followup fixes for MySQL Bug #13889741: HANDLE_FATAL_SIGNAL IN _DB_ENTER_ | HANDLE_FATAL_SIGNAL IN STRNLEN
-
- 10 Nov, 2012 2 commits
-
-
Vladislav Vaintroub authored
Take into account that length of strings passed down to this function can be up to FN_REFLEN+1 bytes. including terminating zero. The overwrite was caused by incomplete fix to MySQL Bug # 44834
-
Igor Babaev authored
If triggers are used for an insert/update/delete statement than the values of all virtual columns must be computed as any of them may be used by the triggers.
-
- 09 Nov, 2012 3 commits
-
-
Sergei Golubchik authored
add a test case for MySQL Bug #13889741: HANDLE_FATAL_SIGNAL IN _DB_ENTER_ | HANDLE_FATAL_SIGNAL IN STRNLEN
-
unknown authored
-
unknown authored
Made information_schema_all_engines stable by adding "sorted_result".
-
- 08 Nov, 2012 3 commits
-
-
Vladislav Vaintroub authored
-
unknown authored
-
unknown authored
-
- 07 Nov, 2012 1 commit
-
-
unknown authored
-
- 06 Nov, 2012 1 commit
-
-
unknown authored
-
- 02 Nov, 2012 1 commit
-
-
unknown authored
-
- 01 Nov, 2012 3 commits
- 31 Oct, 2012 4 commits
-
-
unknown authored
-
Michael Widenius authored
mysql-test/r/partition.result: Added test case mysql-test/t/partition.test: Added test case sql/ha_partition.cc: Removed printing of not initialized variable storage/maria/ha_maria.cc: Don't copy variables that are not initialized
-
Michael Widenius authored
storage/maria/ma_test2.c: Problem was that rnd() generated bigger value than allocated array
-
unknown authored
-
- 09 Oct, 2012 1 commit
-
-
unknown authored
-
- 14 Oct, 2012 1 commit
-
-
unknown authored
Empty result after reading const tables now works for subqueries.
-
- 02 Oct, 2012 1 commit
-
-
unknown authored
Check ability of index to be NULL as it made in MyISAM. UNIQUE with NULL could have several NULL entries so we have to continue even if ve have found a row.
-
- 27 Sep, 2012 2 commits
- 26 Sep, 2012 3 commits
-
-
Sergei Golubchik authored
-
Sergei Golubchik authored
-
unknown authored
- Fix some warnings in newer GCC (-Werror ...). - Fix wrong STACK_DIRECTION detected by configure due to compiler inlining.
-
- 25 Sep, 2012 1 commit
-
-
Sergei Golubchik authored
-
- 26 Sep, 2012 1 commit
-
-
unknown authored
-
- 24 Sep, 2012 2 commits
-
-
Sergei Golubchik authored
-
Sergei Golubchik authored
-
- 14 Sep, 2012 1 commit
-
-
unknown authored
Analysis: The queries in question use the [unique | index]_subquery execution methods. These methods reuse the ref keys constructed by create_ref_for_key(). The way create_ref_for_key() works is that it doesn't store in ref.key_copy[] store_key elements that represent constants. In particular it doesn't store the store_key for NULL constants. The execution of [unique | index]_subquery calls subselect_uniquesubquery_engine::copy_ref_key, which in addition to copy the left IN argument into a index lookup key, is supposed to detect if the left IN argument contains NULLs. Since the store_key for the NULL constant is not copied into the key array, the null is not detected, and execution erroneously proceeds as if it should look for a complete match. Solution: The solution (unlike MySQL) is to reuse already computed information about NULL presence. Item_in_optimizer::val_int already finds out if the left IN operand contains NULLs. The fix propagates this to the execution methods subselect_[unique | index]subquery_engine::exec so it knows if there were NULL values independent of the presence of keys. In addition the patch siplifies copy_ref_key() and the logic that hanldes the case of NULLs in the left IN operand.
-
- 11 Sep, 2012 1 commit
-
-
Joerg Bruehe authored
-
- 05 Sep, 2012 1 commit
-
-
Tor Didriksen authored
In fill_schema_table_by_open(): free item list before restoring active arena. sql/sql_show.cc: Replaced i_s_arena.free_items with DBUG_ASSERT(i_s_arena.free_list == NULL) (there's nothing to free in that list)
-
- 03 Sep, 2012 1 commit
-
-
unknown authored
No commit message
-
- 31 Aug, 2012 1 commit
-
-
Annamalai Gurusami authored
THOUGH IT IS NOT. The following error message is misleading because it claims that the BLOB space is not counted. "ERROR 1118 (42000): Row size too large. The maximum row size for the used table type, not counting BLOBs, is 8126. You have to change some columns to TEXT or BLOBs" When the ROW_FORMAT=compact or ROW_FORMAT=REDUNDANT is used, the BLOB prefix is stored inline along with the row. So the above error message is changed as follows depending on the row format used: For ROW_FORMAT=COMPRESSED or ROW_FORMAT=DYNAMIC, the error message is as follows: "ERROR 42000: Row size too large (> 8126). Changing some columns to TEXT or BLOB may help. In current row format, BLOB prefix of 0 bytes is stored inline." For ROW_FORMAT=COMPACT or ROW_FORMAT=REDUNDANT, the error message is as follows: "ERROR 42000: Row size too large (> 8126). Changing some columns to TEXT or BLOB or using ROW_FORMAT=DYNAMIC or ROW_FORMAT=COMPRESSED may help. In current row format, BLOB prefix of 768 bytes is stored inline." rb://1252 approved by Marko Makela
-