- 05 Nov, 2009 1 commit
-
-
Mikael Ronstrom authored
BUG#48447, BUG#48161, fixed a regression from fix of BUG#6045, where binary collations can use indexes/partition pruning for cases using equality conditions, however it cannot be used for any other condition like <, >, <=, >=, <>, also added test case for verification of BUG#47774 in this patch
-
- 04 Nov, 2009 1 commit
-
-
Mikael Ronstrom authored
Fixed a use of non-initialised variable, cannot use NULL flags if RANGE == NO_MAX_RANGE or NO_MIN_RANGE, so need to check NULL flags after checking the RANGE isn't NO_MAX_RANGE
-
- 03 Nov, 2009 2 commits
-
-
Mikael Ronstrom authored
-
Alexander Nozdrin authored
-
- 02 Nov, 2009 7 commits
-
-
Mikael Ronstrom authored
-
Alexander Barkov authored
from mysql-next-mr-bar
-
Alexander Nozdrin authored
```--------------------------------------------------------- revno: 2599.178.12 revision-id: alik@mysql.com-20080812161845-we7cx9f22yrghob1 committer: Alexander Nozdrin <alik@mysql.com> branch nick: 6.0-rt-build timestamp: Tue 2008-08-12 20:18:45 +0400 message: Fix memory leak. ``` ---------------------------------------------------------
-
Mikael Ronstrom authored
Fixed a few bugs in hex string generation, in call to val_str for partition expressions, also made code reusable for DEFAULT handling to fix BUG#48464 by introducing function get_cs_converted_string_value, added partition_utf8 test case for UTF8 outputs
-
Alexander Nozdrin authored
-
Mikael Ronstrom authored
-
Mikael Ronstrom authored
-
- 31 Oct, 2009 4 commits
-
-
Mikael Ronstrom authored
-
Mikael Ronstrom authored
-
Alexander Nozdrin authored
-
Alexander Nozdrin authored
-
- 30 Oct, 2009 4 commits
-
-
Mikael Ronstrom authored
-
Mikael Ronstrom authored
Fixed such that we fail if using integer constants for character set fields, now need to have correct constant types
-
Mikael Ronstrom authored
Fixed so that character set constants are encoded as hex strings in frm file, but as utf8 strings in the same manner as default values in show create table and information schema tables
-
Mikael Ronstrom authored
-
- 29 Oct, 2009 11 commits
-
-
Mikael Ronstrom authored
-
Marc Alff authored
Backport for 5.5 In non debug builds, the statements: - SHOW PROCEDURE CODE - SHOW FUNCTION CODE used to fail with a "syntax error", which is misleading. These statements have been changed to return the following error for non debug builds: ERROR HY000: The 'SHOW PROCEDURE|FUNCTION CODE' feature is disabled; you need MySQL built with '--with-debug' to have it working For debug builds (./configure --with-debug), nothing is changed.
-
Kristofer Pettersson authored
-
Marc Alff authored
Backport for 5.5
-
Marc Alff authored
-
Marc Alff authored
Backport to 5.5
-
Alexander Nozdrin authored
-
Mikael Ronstrom authored
BUG#48397, set key_part->length to key_part->store_length isn't correct, store_length is a bit longer
-
Kristofer Pettersson authored
When the query cache is disabled, the server shouldn't attempt to take the query cache mutex. By using the command line option --query_cache_type=0, the user can disable (backport from mysql-pe) mysql-test/t/query_cache_disabled-master.opt: * added test case for bug38551 mysql-test/t/query_cache_disabled.test: * added test case for bug38551 sql/set_var.cc: * Added before-trigger to verify that query_cache_type wasn't turned off or on during runtime. sql/set_var.h: * Changed order on how the enumeration is processed. By first projecting the character representation of the variable to a temporary integer we can have one function instead of two to check if the value is valid. sql/share/errmsg-utf8.txt: * Added error message for query cache disabled state sql/sql_cache.cc: * If the query cache is disabled at start up, shorten the execution path and avoid grabbing the query cache mutex each time the invalidate interface methods are called. sql/sql_cache.h: * Added new methods to set the query cache into a disabled state.
-
Alexander Barkov authored
Re-Allowing sr_YU with a "deprecated" warning.
-
Alexey Botchkov authored
per-file comments: mysql-test/r/mysql_upgrade.result result updated mysql-test/t/mysql_upgrade.test --skip-verbose option added to the call
-
- 28 Oct, 2009 10 commits
-
-
Mikael Ronstrom authored
Fixed code review change to ensure that VALUES constants are of the same result type as the field they are constants for
-
Mikael Ronstrom authored
-
Mikael Ronstrom authored
-
Mikael Ronstrom authored
-
Mattias Jonsson authored
-
Tor Didriksen authored
-
Tor Didriksen authored
Item_sum::set_aggregator() may be called multiple times during query preparation. On subsequent calls: verify that the aggregator type is the same, and re-use the existing Aggregator. sql/item_sum.cc: In Item_sum::set_aggregator(): re-use existing Aggregator if already set. Remove some friend declarations, add some accessor functions. Cleanup some DBUG_ENTER and DBUG_RETURN code. sql/item_sum.h: Make some member fields private, add accessors instead. Remove some un-necessary friend declarations. Remove some default arguments from constructors. sql/opt_sum.cc: Use accessor functions in Item_sum. sql/sql_select.cc: Fix mis-spelled DBUG_ENTER text. Use accessor functions in Item_sum. sql/sql_yacc.yy: Use explicit true/false rather than default arguments when constructing Item_sum_xxx objects.
-
Alexey Botchkov authored
(backport) mysql_upgrade script accepts --upgrade-system-tables option, fixing only system tables in this case. per-file comments: client/mysql_upgrade.c WL#4991 mysql_upgrade --fix-privilege-tables --upgrade-system-tables option added. if it is set, the tool won't look for the mysqlcheck then run_mysqlcheck_fixnames() and run_mysqlcheck_upgrade won't be called. mysql-test/r/mysql_upgrade.result WL#4991 mysql_upgrade --fix-privilege-tables test result added mysql-test/t/mysql_upgrade.test WL#4991 mysql_upgrade --fix-privilege-tables test case added
-
Alexander Nozdrin authored
-
Alexander Nozdrin authored
-