- 12 Jan, 2007 1 commit
-
-
gluh@mysql.com/eagle.(none) authored
into mysql.com:/home/gluh/MySQL/Merge/5.0
-
- 11 Jan, 2007 4 commits
-
-
gkodinov/kgeorge@rakia.gmz authored
into rakia.gmz:/home/kgeorge/mysql/autopush/B25106-5.0-opt
-
gkodinov/kgeorge@macbook.gmz authored
aliases ignored When a column reference to a column in JOIN USING is resolved and a new Item is created for this column the user defined name was lost. This fix preserves the alias by setting the name of the new Item to the original alias.
-
holyfoot/hf@mysql.com/hfmain.(none) authored
into mysql.com:/d2/hf/mr10/my50-mr10
-
mmj@tiger.mmj.dk authored
into tiger.mmj.dk:/Users/mmj/bktrees/mysql-5.0
-
- 10 Jan, 2007 11 commits
-
-
kent@mysql.com/kent-amd64.(none) authored
Corrected default for --disable-grant-options
-
igor@olga.mysql.com authored
into olga.mysql.com:/home/igor/mysql-5.0-opt
-
holyfoot/hf@mysql.com/hfmain.(none) authored
into mysql.com:/d2/hf/mr10/my50-mr10
-
kent@mysql.com/kent-amd64.(none) authored
Removed line accidently inserted when correcting bug#18526
-
holyfoot/hf@mysql.com/hfmain.(none) authored
into mysql.com:/d2/hf/mr10/my50-mr10
-
gluh@mysql.com/eagle.(none) authored
-
gluh@mysql.com/eagle.(none) authored
into mysql.com:/home/gluh/MySQL/Merge/5.0-opt
-
gluh@mysql.com/eagle.(none) authored
2nd version During tmp tables cleanup we get the handler for temporary table and delete table using handler method.
-
igor@olga.mysql.com authored
In the method Item_field::fix_fields we try to resolve the name of the field against the names of the aliases that occur in the select list. This is done by a call of the function find_item_in_list. When this function finds several occurrences of the field name it sends an error message to the error queue and returns 0. Yet the code did not take into account that find_item_in_list could return 0 and tried to dereference the returned value.
-
tsmith@siva.hindu.god authored
- configure --disable-grant-options defines DISABLE_GRANT_OPTIONS - configure.js/cmake also updated - if DISABLE_GRANT_OPTIONS is defined, mysqld no longer recognizes: --bootstrap --init-file --skip-grant-tables Scripts which rely on those three options are modified to check the environment for MYSQLD_BOOTSTRAP; it should be set to the full path of a mysqld which does handle those options. For example: $ export MYSQLD_BOOTSTRAP $ MYSQLD_BOOTSTRAP=/path/to/full/MySQL/bin/mysqld $ mysql_install_db $ make test
-
igor@olga.mysql.com authored
into olga.mysql.com:/home/igor/mysql-5.0-opt
-
- 09 Jan, 2007 14 commits
-
-
joerg@trift2. authored
support-files/MySQL-shared-compat.spec.sh : Dummy, irrelevant change - just trigger a new build.
-
evgen@moonbone.local authored
used. The Item::save_in_field() function is called from fill_record() to fill the new row with data while execution of the CREATE TABLE ... SELECT statement. Item::save_in_field() calls val_xxx() methods in order to get values. val_xxx() methods do not take into account the result field. Due to this Item_func_set_user_var::val_xxx() methods returns values from the original table, not from the temporary one. The save_in_field() member function is added to the Item_func_set_user_var class. It detects whether the result field should be used and properly updates the value of the user variable.
-
igor@olga.mysql.com authored
into olga.mysql.com:/home/igor/mysql-5.0-opt
-
evgen@moonbone.local authored
A BINARY field is represented by the Field_string class. The space character is used as the filler for unused characters in such a field. But a BINARY field should use \x00 instead. Field_string:reset() now detects whether the current field is a BINARY one and if so uses the \x00 character as a default value filler.
-
evgen@moonbone.local authored
into moonbone.local:/home/evgen/bk-trees/mysql-5.0-opt
-
igor@olga.mysql.com authored
into olga.mysql.com:/home/igor/dev-opt/mysql-5.0-opt-bug25027
-
thek@kpdesk.mysql.com authored
into kpdesk.mysql.com:/home/thek/dev/mysql-5.0-build
-
holyfoot/hf@mysql.com/hfmain.(none) authored
into mysql.com:/d2/hf/opt/my50-opt
-
thek@kpdesk.mysql.com authored
into kpdesk.mysql.com:/home/thek/dev/bug23010/my50-bug23010
-
thek@kpdesk.mysql.com authored
into kpdesk.mysql.com:/home/thek/dev/bug23010/my41-fix23010
-
thek@kpdesk.mysql.com authored
-
evgen@moonbone.local authored
into moonbone.local:/home/evgen/bk-trees/mysql-5.0-opt
-
igor@olga.mysql.com authored
into olga.mysql.com:/home/igor/dev-opt/mysql-5.0-opt-bug24345
-
holyfoot/hf@mysql.com/hfmain.(none) authored
into mysql.com:/d2/hf/opt/my50-opt
-
- 05 Jan, 2007 3 commits
-
-
kent@mysql.com/kent-amd64.(none) authored
into mysql.com:/home/kent/bk/tmp/mysql-5.0-build
-
kent@mysql.com/kent-amd64.(none) authored
Add CFLAGS to gcc call with --print-libgcc-file, to make sure the correct "libgcc.a" path is returned for the 32/64 bit architecture
-
gkodinov/kgeorge@macbook.gmz authored
The optimizer removes expressions from GROUP BY/DISTINCT if they happen to participate in a <expression> = <const> predicates of the WHERE clause (the idea being that if it's always equal to a constant it can't have multiple values). However for predicates where the expression and the constant item are of different result type this is not valid (e.g. a string column compared to 0). Fixed by additional check of the result types of the expression and the constant and if they differ the expression don't get removed from the group by list.
-
- 04 Jan, 2007 6 commits
-
-
mmj@tiger.mmj.dk authored
into tiger.mmj.dk:/Users/mmj/bktrees/mysql-5.0-build
-
mmj@tiger.mmj.dk authored
Patch from Alfredo for TARGET_FAT_BINARY
-
mmj@tiger.mmj.dk authored
into tiger.mmj.dk:/Users/mmj/bktrees/mysql-5.0-build
-
mmj@tiger.mmj.dk authored
Add patch from Alfredo for TARGET_FAT_BINARY
-
holyfoot/hf@mysql.com/hfmain.(none) authored
into mysql.com:/d2/hf/opt/my50-opt
-
holyfoot/hf@mysql.com/hfmain.(none) authored
into mysql.com:/d2/hf/opt/my50-opt
-
- 03 Jan, 2007 1 commit
-
-
igor@olga.mysql.com authored
This bug appeared after the patch for bug 21390 that had added some code to handle outer joins with no matches after substitution of a const table in an efficient way. That code as it is cannot be applied to the case of nested outer join operations. Being applied to the queries with nested outer joins the code can cause crashes or wrong result sets. The fix blocks row substitution for const inner tables of an outer join if the inner operand is not a single table.
-