- 09 Oct, 2007 5 commits
-
-
mhansson@dl145s.mysql.com authored
into dl145s.mysql.com:/data0/mhansson/bug31160/my50-bug31160
-
mhansson@dl145s.mysql.com authored
into dl145s.mysql.com:/data0/mhansson/bug31160/my50-bug31160
-
mhansson/martin@linux-st28.site authored
Even though it returns NULL, the MAKETIME function did not have this property set, causing a failed assertion (designed to catch exactly this). Fixed by setting the nullability property of MAKETIME().
-
mhansson/martin@linux-st28.site authored
into linux-st28.site:/home/martin/mysql/src/bug30832-again-push/my50-bug30832-again
-
mhansson/martin@linux-st28.site authored
Completion of previous patch. Negative number were denied as the second argument to NAME_CONST.
-
- 05 Oct, 2007 10 commits
-
-
holyfoot/hf@hfmain.(none) authored
into mysql.com:/home/hf/work/30286/my50-30286
-
mhansson@dl145s.mysql.com authored
into dl145s.mysql.com:/data0/mhansson/bug30942/my50-bug30942
-
holyfoot/hf@hfmain.(none) authored
into mysql.com:/home/hf/work/30286/my50-30286
-
holyfoot/hf@mysql.com/hfmain.(none) authored
into mysql.com:/home/hf/work/30286/my41-30286
-
holyfoot/hf@hfmain.(none) authored
into mysql.com:/home/hf/work/30286/my50-30286
-
holyfoot/hf@mysql.com/hfmain.(none) authored
into mysql.com:/home/hf/work/30286/my41-30286
-
holyfoot/hf@hfmain.(none) authored
into mysql.com:/home/hf/work/30286/my50-30286
-
holyfoot/hf@hfmain.(none) authored
into mysql.com:/home/hf/work/30286/my50-30286
-
holyfoot/hf@mysql.com/hfmain.(none) authored
As the result of DOUBLE claculations can be bigger than DBL_MAX constant we use in code, we shouldn't use this constatn as a biggest possible value. Particularly the rtree_pick_key function set 'min_area= DBL_MAX' relying that any rtree_area_increase result will be less so we return valid key. Though in rtree_area_increase function we calculate the area of the rectangle, so the result can be 'inf' if the rectangle is huge enough, which is bigger than DBL_MAX. Code of the rtree_pick_key modified so we always return a valid key.
-
gluh@mysql.com/eagle.(none) authored
-
- 04 Oct, 2007 3 commits
-
-
gluh@mysql.com/eagle.(none) authored
added check for hidden I_S tables for 'show columns|keys' commands
-
mhansson@dl145s.mysql.com authored
into dl145s.mysql.com:/data0/mhansson/bug30942/my50-bug30942
-
mhansson/martin@linux-st28.site authored
The function str_to_date has a field to say whether it's invoked constant arguments. But this member was not initialized, causing the function to think that it could use a cache of the format type when said cache was in fact not initialized. Fixed by initializing the field to false.
-
- 03 Oct, 2007 3 commits
-
-
holyfoot/hf@mysql.com/hfmain.(none) authored
end-of-line check missed in Gis_read_stream::get_next_word, what can lead to crashes (expecially with NULL strings). End-of-line check added
-
gshchepa/uchum@gleb.loc authored
into gleb.loc:/home/uchum/work/bk/5.0-opt
-
gshchepa/uchum@gleb.loc authored
Bug #31077: post-commit fix.
-
- 02 Oct, 2007 8 commits
-
-
gshchepa/uchum@gleb.loc authored
into gleb.loc:/home/uchum/work/bk/5.0-opt
-
gshchepa/uchum@gleb.loc authored
Bug #31077: post-commit fix.
-
gshchepa/uchum@gleb.loc authored
into gleb.loc:/home/uchum/work/bk/5.0-opt
-
gkodinov/kgeorge@magare.gmz authored
-
gkodinov/kgeorge@magare.gmz authored
into magare.gmz:/home/kgeorge/mysql/autopush/B28702-vg-5.0-opt
-
gkodinov/kgeorge@magare.gmz authored
-
mhansson@dl145s.mysql.com authored
into dl145s.mysql.com:/data0/mhansson/bug30832/my50-bug30832
-
evgen@moonbone.local authored
into moonbone.local:/work/31095-bug-5.0-opt-mysql
-
- 01 Oct, 2007 4 commits
-
-
evgen@moonbone.local authored
The Item_func_rollup_const class is used for wrapping constants to avoid wrong result for ROLLUP queries with DISTINCT and a constant in the select list. This class is also used to wrap up a NULL constant but its null_value wasn't set accordingly. This led to a server crash. Now the null_value of an object of the Item_func_rollup_const class is set by its fix_length_and_dec member function.
-
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
-
- 29 Sep, 2007 1 commit
-
-
evgen@moonbone.local authored
Corrected test case for the bug#29908.
-
- 28 Sep, 2007 5 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/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.
-
- 27 Sep, 2007 1 commit
-
-
evgen@sunlight.local authored
into sunlight.local:/local_work/29908-bug-5.0-opt-mysql
-