- 22 Nov, 2007 5 commits
-
-
kaa@polly.(none) authored
into polly.(none):/home/kaa/src/opt/mysql-5.1-opt
-
kaa@polly.(none) authored
into polly.(none):/home/kaa/src/opt/bug32221/my51-bug31445
-
kaa@polly.(none) authored
We do not have any executables in libmysql/release/ anymore.
-
kaa@polly.(none) authored
into polly.(none):/home/kaa/src/opt/mysql-5.1-opt
-
kaa@polly.(none) authored
into polly.(none):/home/kaa/src/opt/bug32221/my51-bug31445
-
- 21 Nov, 2007 3 commits
-
-
gkodinov/kgeorge@magare.gmz authored
-
gkodinov/kgeorge@magare.gmz authored
into magare.gmz:/home/kgeorge/mysql/work/B30788-5.1-opt
-
gkodinov/kgeorge@magare.gmz authored
Index lookup does not always guarantee that we can simply remove the relevant conditions from the WHERE clause. Reasons can be e.g. conversion errors, partial indexes etc. The optimizer was removing these parts of the WHERE condition without any further checking. This leads to "false positives" when using indexes. Fixed by checking the index reference conditions (using WHERE) when using indexes with sub-queries.
-
- 20 Nov, 2007 6 commits
-
-
sergefp@foxhole.(none) authored
into mysql.com:/home/psergey/mysql-5.1-bug30573
-
holyfoot/hf@mysql.com/hfmain.(none) authored
-
holyfoot/hf@hfmain.(none) authored
into mysql.com:/home/hf/work/31868/my51-31868
-
holyfoot/hf@hfmain.(none) authored
into mysql.com:/home/hf/work/31868/my51-31868
-
holyfoot/hf@hfmain.(none) authored
into mysql.com:/home/hf/work/31868/my51-31868
-
sergefp@mysql.com authored
The problem: ha_partition::read_range_first() could return a record that is outside of the scanned range. If that record happened to be in the next subsequent range, it would satisfy the WHERE and appear in the output twice. (we would get it the second time when scanning the next subsequent range) Fix: Made ha_partition::read_range_first() check if the returned recod is within the scanned range, like other read_range_first() implementations do.
-
- 19 Nov, 2007 7 commits
-
-
kaa@polly.(none) authored
crashes. MySQL distributions contain a number of programs that are used only by the MySQL test suite internally, i.e. they are not indended to be invoked directly by a user. As a result, such programs are not documented, do not have any built-in help or proper error reporting, which may confuse users. This patch fixes the problem with the following changes: - mytest, libmysqltest and all references to them were removed from the distribution since they are not used anymore - bug25714 now displays an error message when run with incorrect arguments or with the --help option - mysql_client_test now does not call abort() in case of errors, instead it does a clean exit() with a proper error status.
-
kaa@polly.(none) authored
into polly.(none):/home/kaa/src/opt/mysql-5.1-opt
-
kaa@polly.(none) authored
into polly.(none):/home/kaa/src/opt/mysql-5.1-opt
-
kaa@polly.(none) authored
into polly.(none):/home/kaa/src/opt/mysql-5.0-opt
-
kaa@polly.(none) authored
into polly.(none):/home/kaa/src/opt/bug32376/my51-bug26215
-
kaa@polly.(none) authored
disables the option explicitely. Changed the option location in code so that --help will show it in lexical option order. This is for bug #26215: mysql command line client should not strip comments from SQL statements
-
gluh@mysql.com/eagle.(none) authored
added check for the result of mysql_unpack_partition()
-
- 18 Nov, 2007 2 commits
-
-
holyfoot/hf@mysql.com/hfmain.(none) authored
-
gshchepa/uchum@gleb.loc authored
into gleb.loc:/work/bk/5.1-opt
-
- 17 Nov, 2007 11 commits
-
-
holyfoot/hf@mysql.com/hfmain.(none) authored
failing 'INSTALL PLUGIN' statement doesn't work in embedded server as we disable library loading there. Fixed by enabling loading libraries (#define HAVE_DLOPEN), what also makes UDF working in the embedded server.
-
gshchepa/uchum@gleb.loc authored
into gleb.loc:/work/bk/5.0-opt
-
gshchepa/uchum@gleb.loc authored
Comparison of a BIGINT NOT NULL column with a constant arithmetic expression that evaluates to NULL caused error 1048: "Column '...' cannot be null". Made convert_constant_item() check if the constant expression is NULL before attempting to store it in a field. Attempts to store NULL in a NOT NULL field caused query errors.
-
holyfoot/hf@hfmain.(none) authored
into mysql.com:/home/hf/work/31158/my51-31158
-
holyfoot/hf@hfmain.(none) authored
into mysql.com:/home/hf/work/31158/my50-31158
-
holyfoot/hf@mysql.com/hfmain.(none) authored
into mysql.com:/home/hf/work/31158/my41-31158
-
holyfoot/hf@hfmain.(none) authored
into mysql.com:/home/hf/work/31158/my50-31158
-
holyfoot/hf@hfmain.(none) authored
into mysql.com:/home/hf/work/31158/my51-31158
-
holyfoot/hf@hfmain.(none) authored
into mysql.com:/home/hf/work/31158/my51-31158
-
holyfoot/hf@mysql.com/hfmain.(none) authored
-
holyfoot/hf@hfmain.(none) authored
into mysql.com:/home/hf/work/31158/my50-31158
-
- 16 Nov, 2007 6 commits
-
-
kaa@polly.(none) authored
into polly.(none):/home/kaa/src/opt/mysql-5.1-opt
-
kaa@polly.(none) authored
into polly.(none):/home/kaa/src/opt/mysql-5.1-opt
-
kaa@polly.(none) authored
into polly.(none):/home/kaa/src/opt/mysql-5.0-opt
-
kaa@polly.(none) authored
into polly.(none):/home/kaa/src/opt/bug32241/my51-bug29131
-
kaa@polly.(none) authored
checked for each record' The problem was in incorrectly calculated length of the buffer used to store a hexadecimal representation of an index map in select_describe(). This could result in buffer overrun and stack corruption under some circumstances. Fixed by correcting the calculation.
-
gluh@eagle.(none) authored
into mysql.com:/home/gluh/MySQL/Merge/5.1-opt
-