- 05 Jun, 2007 3 commits
-
-
istruewing@chilla.local authored
into chilla.local:/home/mydev/mysql-5.1-axmrg
-
istruewing@chilla.local authored
into chilla.local:/home/mydev/mysql-5.1-axmrg
-
istruewing@chilla.local authored
into chilla.local:/home/mydev/mysql-5.0-axmrg
-
- 04 Jun, 2007 8 commits
-
-
svoj@april.(none) authored
into mysql.com:/home/svoj/devel/mysql/BUG27141/mysql-5.1-engines
-
svoj@mysql.com/april.(none) authored
Original problem was fixed by Magnus (see BUG25807). Currently only windows debug build causes assertion failure. This patch assures that my_tell gets correct file descriptor on any platform by DBUG_ASSERT macro.
-
igor@olga.mysql.com authored
into olga.mysql.com:/home/igor/mysql-5.1-opt
-
igor@olga.mysql.com authored
-
igor@olga.mysql.com authored
into olga.mysql.com:/home/igor/mysql-5.1-opt-merge
-
igor@olga.mysql.com authored
-
mhansson@dl145s.mysql.com authored
into dl145s.mysql.com:/dev/shm/mhansson/my50-bug27741
-
igor@olga.mysql.com authored
into olga.mysql.com:/home/igor/mysql-5.1-opt-merge
-
- 03 Jun, 2007 12 commits
-
-
mhansson@dl145s.mysql.com authored
into dl145s.mysql.com:/dev/shm/mhansson/my51-bug27741-mpush
-
evgen@moonbone.local authored
Post merge fix for the bug#28494.
-
igor@olga.mysql.com authored
into olga.mysql.com:/home/igor/dev-opt/mysql-5.0-opt-bug28728
-
evgen@moonbone.local authored
into moonbone.local:/mnt/gentoo64/work/test-5.1-opt-mysql
-
evgen@moonbone.local authored
into moonbone.local:/mnt/gentoo64/work/test-5.0-opt-mysql
-
evgen@moonbone.local authored
Corrected test case result for the bug#28494. item_func.h, item_func.cc: Corrected function names after fix for the bug#28494.
-
evgen@moonbone.local authored
into moonbone.local:/mnt/gentoo64/work/test-5.0-opt-mysql
-
evgen@moonbone.local authored
Extended test case for the bug#28494.
-
igor@olga.mysql.com authored
into olga.mysql.com:/home/igor/dev-opt/mysql-5.0-opt-bug28728
-
gkodinov/kgeorge@macbook.gmz authored
into macbook.gmz:/Users/kgeorge/mysql/work/B26162-5.0-opt
-
gkodinov/kgeorge@macbook.gmz authored
The value of "low-priority-updates" option and the LOW PRIORITY prefix was taken into account at parse time. This caused triggers (among others) to ignore this flag (if supplied for the DML statement). Moved reading of the LOW_PRIORITY flag at run time. Fixed an incosistency when handling SET GLOBAL LOW_PRIORITY_UPDATES : now it is in effect for delayed INSERTs. Tested by checking the effect of LOW_PRIORITY flag via a trigger.
-
evgen@moonbone.local authored
into moonbone.local:/mnt/gentoo64/work/test-5.1-opt-mysql
-
- 02 Jun, 2007 10 commits
-
-
igor@olga.mysql.com authored
into olga.mysql.com:/home/igor/dev-opt/mysql-5.0-opt-bug28728
-
evgen@moonbone.local authored
into moonbone.local:/mnt/gentoo64/work/test-5.0-opt-mysql
-
evgen@moonbone.local authored
Post fix for bug#28494. The Item_func_set_user_var::check method now silently doesn't use result_field if it isn't defined.
-
evgen@moonbone.local authored
into moonbone.local:/mnt/gentoo64/work/test-5.1-opt-mysql
-
igor@olga.mysql.com authored
into olga.mysql.com:/home/igor/dev-opt/mysql-5.0-opt-bug28728
-
evgen@moonbone.local authored
into moonbone.local:/mnt/gentoo64/work/test-5.0-opt-mysql
-
evgen@moonbone.local authored
This is an additional fix. Item::val_xxx methods are supposed to use original data source and Item::val_xxx_result methods to use the item's result field. But for the Item_func_set_user_var class val_xxx_result methods were mapped to val_xxx methods. This leads, in particular, to producing bad sort keys and thus wrong order of the result set of queries with group by/order by clauses. The set of val_xxx_result methods is added to the Item_func_set_user_var class. It's the same as the val_xxx set of method but uses the result_field to return a value.
-
igor@olga.mysql.com authored
using a derived table over a grouping subselect. This crash happens only when materialization of the derived tables requires creation of auxiliary temporary table, for example when a grouping operation is carried out with usage of a temporary table. The crash happened because EXPLAIN EXTENDED when printing the query expression made an attempt to use the objects created in the mem_root of the temporary table which has been already freed by the moment when printing is called. This bug appeared after the method Item_field::print() had been introduced.
-
sergefp@mysql.com authored
-
igor@olga.mysql.com authored
-
- 01 Jun, 2007 7 commits
-
-
ibabaev@bk-internal.mysql.com authored
into bk-internal.mysql.com:/data0/bk/mysql-5.0-opt
-
igor@olga.mysql.com authored
into olga.mysql.com:/home/igor/mysql-5.1-opt
-
evgen@moonbone.local authored
To avoid unnecessary work the mysql_alter_table function takes the list of table fields and applies all changes to it (drops/moves/renames/etc). Then this function compares the new list and the old one. If the changes require only .frm to be modified then the actual data isn't copied. To detect changes all columns attributes but names are compared. When a column has been moved and has replaced another column with the same attributes except name the mysql_alter_table function wrongly decides that two fields has been just renamed. As a result the data from the moved column and from all columns after it is not copied. Now the mysql_alter_table function forces table data copying by setting the need_copy_table flag when it finds a moved column. The flag is set at the stage when the modified fields are created.
-
kostja@bodhi.(none) authored
into bodhi.(none):/opt/local/work/mysql-5.1-runtime
-
kostja@bodhi.(none) authored
-
mhansson@dl145s.mysql.com authored
into dl145s.mysql.com:/dev/shm/mhansson/my51-bug27741-mpush
-
kostja@bodhi.(none) authored
into bodhi.(none):/opt/local/work/mysql-5.1-runtime
-