- 11 Jan, 2007 1 commit
-
-
gluh@mysql.com/eagle.(none) authored
-
- 10 Jan, 2007 5 commits
-
-
gluh@eagle.(none) authored
into mysql.com:/home/gluh/MySQL/Merge/5.1-opt
-
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
into olga.mysql.com:/home/igor/mysql-5.0-opt
-
- 09 Jan, 2007 11 commits
-
-
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
-
gluh@mysql.com/eagle.(none) authored
Unencode internal db & table name
-
holyfoot/hf@mysql.com/hfmain.(none) authored
into mysql.com:/d2/hf/opt/my50-opt
-
evgen@moonbone.local authored
into moonbone.local:/home/evgen/bk-trees/mysql-5.0-opt
-
holyfoot/hf@hfmain.(none) authored
into mysql.com:/d2/hf/opt/my51-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
-
- 08 Jan, 2007 2 commits
-
-
gkodinov/kgeorge@macbook.local authored
added a missing DBUG_RETURN
-
gkodinov/kgeorge@macbook.local authored
into macbook.local:/Users/kgeorge/mysql/work/merge-5.1-opt
-
- 06 Jan, 2007 2 commits
-
-
brian@zim.(none) authored
-
brian@zim.(none) authored
Cleaning up warning for windows. Innodb is compiled but disable on Windows, so it should be fine. NDB wasn't compiled in, which is what caused the issue.
-
- 05 Jan, 2007 1 commit
-
-
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
-
-
brian@zim.(none) authored
into zim.(none):/home/brian/mysql/merge-5.1
-
brian@zim.(none) authored
The CSV format has always relied on numbers being quoted, which doesn't always happen. This fixes that so that numbers can now be unquoted (and the output does this as well so that the log takes up less space).
-
baker@bk-internal.mysql.com authored
into bk-internal.mysql.com:/data0/bk/mysql-5.1-arch
-
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
-
brian@zim.(none) authored
Split out the hidden class from the ha_tina file (probably should have just deleted it...) but this is a bit better.
-
- 03 Jan, 2007 5 commits
-
-
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.
-
gkodinov/kgeorge@rakia.gmz authored
into rakia.gmz:/home/kgeorge/mysql/work/B15439-5.0-opt
-
gkodinov/kgeorge@rakia.gmz authored
Addendum to the fix for bug#15439 : valgrind pb failed
-
holyfoot/hf@mysql.com/hfmain.(none) authored
into mysql.com:/d2/hf/opt/my41-opt
-
holyfoot/hf@mysql.com/hfmain.(none) authored
into mysql.com:/d2/hf/opt/my50-opt
-
- 02 Jan, 2007 7 commits
-
-
holyfoot/hf@hfmain.(none) authored
into mysql.com:/d2/hf/common/my51-common
-
holyfoot/hf@mysql.com/hfmain.(none) authored
-
holyfoot/hf@mysql.com/hfmain.(none) authored
-
holyfoot/hf@mysql.com/hfmain.(none) authored
-
holyfoot/hf@hfmain.(none) authored
into mysql.com:/d2/hf/common/my51-common
-
holyfoot/hf@mysql.com/hfmain.(none) authored
into mysql.com:/d2/hf/common/my50-common
-
holyfoot/hf@mysql.com/hfmain.(none) authored
-