- 03 Oct, 2007 2 commits
-
-
gshchepa/uchum@gleb.loc authored
into gleb.loc:/home/uchum/work/bk/5.1-opt
-
gshchepa/uchum@gleb.loc authored
Bug #31077: post-commit fix.
-
- 02 Oct, 2007 1 commit
-
-
gshchepa/uchum@gleb.loc authored
Bug #31077: post-commit fix.
-
- 01 Oct, 2007 7 commits
-
-
mhansson@dl145s.mysql.com authored
into dl145s.mysql.com:/data0/mhansson/bug30832/my51-bug30832
-
gshchepa/uchum@gleb.loc authored
mysqldump adds the "-- Dump completed on YYYY-MM-DD hh:mm:ss" string to the end of output if the --comments switch is on. The only way to suppress this line is to use --skip-comments/--compact switch. New switch has been added to the mysqldump client command line: --dump-date. For the compatibility with previous releases, by default the --dump-date is on. The --dump-date switch forces mysqldump to add date to the "-- Dump completed on ..." string at the end of output. The --skip-dump-date switch supresses the output of date string and uses short form of that commentary: "-- Dump completed". --skip-comments or --compact switches disable the whole commentary as usual.
-
gkodinov/kgeorge@magare.gmz authored
-
gkodinov/kgeorge@magare.gmz authored
-
gkodinov/kgeorge@magare.gmz authored
-
gkodinov/kgeorge@magare.gmz authored
-
mhansson/martin@linux-st28.site authored
into linux-st28.site:/home/martin/mysql/src/bug30832/my51-bug30832
-
- 29 Sep, 2007 1 commit
-
-
evgen@moonbone.local authored
Corrected test case for the bug#29908.
-
- 28 Sep, 2007 12 commits
-
-
evgen@moonbone.local authored
into moonbone.local:/work/27990-bug-5.0-opt-mysql
-
evgen@moonbone.local authored
The change_to_use_tmp_fields function leaves the orig_table member of an expression's tmp table field filled for the new Item_field being created. Later orig_table is used by the Field::make_field function to provide some info about original table and field name to a user. This is ok for a field but for an expression it should be empty. The change_to_use_tmp_fields function now resets orig_table member of an expression's tmp table field to prevent providing a wrong info to a user. The Field::make_field function now resets the table_name and the org_col_name variables when the orig_table is set to 0.
-
mhansson/martin@linux-st28.site authored
The NAME_CONST function is required to work correctly with constants only. When executed with functions that return types other than those returned by Item::field_type (string, int, decimal, or real), the result gets cast to one of those types. This cannot happen for constants. Fixed by only allowing constants as arguments to NAME_CONST.
-
gkodinov/kgeorge@magare.gmz authored
into magare.gmz:/home/kgeorge/mysql/work/B30587-5.1-opt
-
gkodinov/kgeorge@magare.gmz authored
into magare.gmz:/home/kgeorge/mysql/autopush/B30587-5.0-opt
-
gkodinov/kgeorge@macbook.gmz authored
When calculating the result length of an integer DIV function the number of decimals was used without checking the result type first. Thus an uninitialized number of decimals was used for some types. This caused an excessive amount of memory to be allocated for the field's buffer and crashed the server. Fixed by using the number of decimals only for data types that can have decimals and thus have valid decimals number.
-
gluh@eagle.(none) authored
into mysql.com:/home/gluh/MySQL/Merge/5.1-opt
-
gluh@mysql.com/eagle.(none) authored
skip the check of directory presence for 'information_schema' name
-
gluh@mysql.com/eagle.(none) authored
view_body_utf8 attribute type is changed to 'escaped string'
-
mhansson@dl145s.mysql.com authored
-
mhansson@dl145s.mysql.com authored
into dl145s.mysql.com:/data0/mhansson/my51-bug30665
-
mhansson/martin@linux-st28.site authored
The optimizer takes different execution paths during EXPLAIN than SELECT, this fix relates only to EXPLAIN, hence no behavior changes. The test of sort keys for ORDER BY was prohibited from considering keys that were mentioned in IGNORE KEYS FOR ORDER BY. This led to two inconsistencies: One was that IGNORE INDEX FOR GROUP BY and IGNORE INDEX FOR ORDER BY gave apparently different EXPLAINs; the latter erroneously claimed to do filesort. The second inconsistency is that the test of sort keys is called twice, finding a sort key the first time but not the second time, leading to the mentioned filesort. Fixed by making the test of sort keys consider all enabled keys on the table. This test rejects keys that are not covering, and for covering keys the hint should be ignored anyway.
-
- 27 Sep, 2007 10 commits
-
-
evgen@sunlight.local authored
into sunlight.local:/local_work/29908-bug-5.0-opt-mysql
-
gkodinov/kgeorge@magare.gmz authored
into magare.gmz:/home/kgeorge/mysql/autopush/B30468-5.1-opt
-
gkodinov/kgeorge@magare.gmz authored
-
gkodinov/kgeorge@magare.gmz authored
into magare.gmz:/home/kgeorge/mysql/autopush/B30468-5.1-opt
-
gkodinov/kgeorge@magare.gmz authored
-
gkodinov/kgeorge@magare.gmz authored
into magare.gmz:/home/kgeorge/mysql/autopush/B30468-5.1-opt
-
gkodinov/kgeorge@magare.gmz authored
-
gkodinov/kgeorge@magare.gmz authored
into magare.gmz:/home/kgeorge/mysql/autopush/B30468-5.0-opt
-
gkodinov/kgeorge@magare.gmz authored
When expanding a * in a USING/NATURAL join the check for table access for both tables in the join was done using the grant information of the first one. Fixed by getting the grant information for the current table while iterating through the columns of the join.
-
gshchepa/uchum@gleb.loc authored
Post-commit fix.
-
- 26 Sep, 2007 5 commits
-
-
gshchepa/uchum@gleb.loc authored
into gleb.loc:/home/uchum/work/bk/5.1-opt
-
gshchepa/uchum@gleb.loc authored
into gleb.loc:/home/uchum/work/bk/5.1-opt
-
gkodinov/kgeorge@magare.gmz authored
-
gkodinov/kgeorge@magare.gmz authored
-
gshchepa@devsrv-b.mysql.com authored
The `SELECT col FROM t WHERE col NOT IN (col, ...) GROUP BY col' crashed in the range optimizer. The get_func_mm_tree function has been modified to check the Item_func_in::array field for the NULL value before using of that value.
-
- 24 Sep, 2007 2 commits
-
-
evgen@sunlight.local authored
into sunlight.local:/local_work/merge-5.1-opt-mysql
-
gkodinov/kgeorge@magare.gmz authored
When storing the VIEW the CREATE VIEW command is reconstructed from the parse tree. While constructing the command string the index hints specified should also be printed. Fixed by adding code to print the index hints when printing a table in the FROM clause.
-