- 10 Mar, 2007 1 commit
-
-
evgen@moonbone.local authored
When the SUBSTRING() function was used over a LONGTEXT field the max_length of the SUBSTRING() result was wrongly calculated and set to 0. As the max_length parameter is used while tmp field creation it limits the length of the result field and leads to printing an empty string instead of the correct result. Now the Item_func_substr::fix_length_and_dec() function correctly calculates the max_length parameter.
-
- 07 Mar, 2007 8 commits
-
-
evgen@moonbone.local authored
Postfix for bug#22331 for windows platform. explain.test, explain.result: Cleanup after bugfix#22331.
-
evgen@moonbone.local authored
into moonbone.local:/mnt/gentoo64/work/25373-bug-5.0-opt-mysql
-
evgen@moonbone.local authored
into moonbone.local:/mnt/gentoo64/work/25373-bug-5.0-opt-mysql
-
evgen@moonbone.local authored
result. For built-in functions like sqrt() function names are hard-coded and can be compared by pointer. But this isn't the case for a used-defined stored functions - names there are dynamical and should be compared as strings. Now the Item_func::eq() function employs my_strcasecmp() function to compare used-defined stored functions names.
-
evgen@moonbone.local authored
away. During optimization stage the WHERE conditions can be changed or even be removed at all if they know for sure to be true of false. Thus they aren't showed in the EXPLAIN EXTENDED which prints conditions after optimization. Now if all elements of an Item_cond were removed this Item_cond is substituted for an Item_int with the int value of the Item_cond. If there were conditions that were totally optimized away then values of the saved cond_value and having_value will be printed instead.
-
igor@olga.mysql.com authored
into olga.mysql.com:/home/igor/dev-opt/mysql-5.0-opt-bug26560
-
gkodinov/kgeorge@magare.gmz authored
into magare.gmz:/home/kgeorge/mysql/autopush/B19342-5.0-opt
-
evgen@moonbone.local authored
into moonbone.local:/mnt/gentoo64/work/25376-bug-5.0-opt-mysql
-
- 06 Mar, 2007 3 commits
-
-
evgen@moonbone.local authored
Functions over sum functions wasn't set up correctly for the ORDER BY clause which leads to a wrong order of the result set. The split_sum_func() function is called now for each ORDER BY item that contains a sum function to set it up correctly.
-
gkodinov/kgeorge@magare.gmz authored
into magare.gmz:/home/kgeorge/mysql/autopush/B19342-5.0-opt
-
gkodinov/kgeorge@macbook.gmz authored
-
- 05 Mar, 2007 2 commits
-
-
evgen@moonbone.local authored
into moonbone.local:/mnt/gentoo64/work/clean-5.0-opt-mysql
-
igor@olga.mysql.com authored
The flag alias_name_used was not set on for the outer references in subqueries. It resulted in replacement of any outer reference resolved against an alias for a full field name when the frm representation of a view with a subquery was generated. If the subquery and the outer query referenced the same table in their from lists this replacement effectively changed the meaning of the view and led to wrong results for selects from this view. Modified several functions to ensure setting the right value of the alias_name_used flag for outer references resolved against aliases.
-
- 03 Mar, 2007 1 commit
-
-
evgen@sunlight.local authored
When the ORDER BY clause gets fixed it's allowed to search in the current item_list in order to find aliased fields and expressions. This is ok for a SELECT but wrong for an UPDATE statement. If the ORDER BY clause will contain a non-existing field which is mentioned in the UPDATE set list then the server will crash due to using of non-existing (0x0) field. When an Item_field is getting fixed it's allowed to search item list for aliased expressions and fields only for selects.
-
- 02 Mar, 2007 8 commits
-
-
gkodinov/kgeorge@magare.gmz authored
-
gkodinov/kgeorge@macbook.gmz authored
-
gkodinov/kgeorge@magare.gmz authored
into magare.gmz:/home/kgeorge/mysql/autopush/B19342-5.0-opt
-
gkodinov/kgeorge@magare.gmz authored
into magare.gmz:/home/kgeorge/mysql/autopush/B19342-5.0-opt
-
gkodinov/kgeorge@macbook.gmz authored
Several problems here : 1. The conversion to double of an hex string const item was not taking into account the unsigned flag. 2. IN was not behaving in the same was way as comparisons when performed over an INT/DATE/DATETIME/TIMESTAMP column and a constant. The ordinary comparisons in that case convert the constant to an INTEGER value and do int comparisons. Fixed the IN to do the same. 3. IN is not taking into account the unsigned flag when calculating <expr> IN (<int_const1>, <int_const2>, ...). Extended the implementation of IN to store and process the unsigned flag for its arguments.
-
gkodinov/kgeorge@magare.gmz authored
into magare.gmz:/home/kgeorge/mysql/autopush/B26537-5.0-opt
-
evgen@sunlight.local authored
Post fix for bug#25122.
-
gkodinov/kgeorge@magare.gmz authored
to return NULL for non-NULL arguments. This is not the case as it can return NULL for invalid hexidecimal strings. Fixed by setting the maybe_null flag.
-
- 01 Mar, 2007 3 commits
-
-
evgen@moonbone.local authored
into moonbone.local:/mnt/gentoo64/work/25122-bug-5.0-opt-mysql
-
evgen@moonbone.local authored
When INSERT is done over a view the table being inserted into is checked to be unique among all views tables. But if the view contains self-joined table an error will be thrown even if all tables are used under different aliases. The unique_table() function now also checks tables' aliases when needed.
-
gkodinov/kgeorge@magare.gmz authored
in build.
-
- 27 Feb, 2007 1 commit
-
-
gluh@mysql.com/eagle.(none) authored
-
- 26 Feb, 2007 3 commits
-
-
gluh@mysql.com/eagle.(none) authored
into mysql.com:/home/gluh/MySQL/Merge/5.0-opt
-
knielsen@ymer.(none) authored
-
evgen@sunlight.local authored
Post fix for bug#23800.
-
- 25 Feb, 2007 1 commit
-
-
evgen@sunlight.local authored
Post fix for bug#23800. Copy the table name of an Item_outer_ref to the conventional memory.
-
- 24 Feb, 2007 2 commits
-
-
evgen@moonbone.local authored
into moonbone.local:/mnt/gentoo64/work/23800-bug1-5.0-opt-mysql
-
evgen@moonbone.local authored
Post fix for bug#23800. The Item_field constructor now increases the select_n_where_fields counter. sql_yacc.yy: Post fix for bug#23800. Take into account fields that might be added by subselects. sql_lex.h: Post fix for bug#23800. Added the select_n_where_fields variable to the st_select_lex class. sql_lex.cc: Post fix for bug#23800. Initialization of the select_n_where_fields variable.
-
- 22 Feb, 2007 7 commits
-
-
monty@mysql.com/hasky.mysql.fi authored
into mysql.com:/home/my/mysql-5.0
-
monty@mysql.com/narttu.mysql.fi authored
into mysql.com:/home/my/mysql-5.0
-
monty@mysql.com/hasky.mysql.fi authored
into mysql.com:/home/my/mysql-5.0
-
monty@mysql.com/narttu.mysql.fi authored
Suppress compiler warnings from bdb and (for the moment) warnings from ndb
-
monty@mysql.com/hasky.mysql.fi authored
into mysql.com:/home/my/mysql-5.0
-
monty@mysql.com/narttu.mysql.fi authored
Fixed a couple of usage of not initialized warnings (unlikely cases)
-
mhansson@dl145s.mysql.com authored
into dl145s.mysql.com:/users/mhansson/mysql/autopush/5.0o-bug24010
-