- 07 Feb, 2006 2 commits
-
-
pekka@mysql.com authored
-
pekka@mysql.com authored
-
- 06 Feb, 2006 6 commits
-
-
igor@rurik.mysql.com authored
into rurik.mysql.com:/home/igor/dev/mysql-5.0-0
-
igor@rurik.mysql.com authored
If check_quick_select returns non-empty range then the function cost_group_min_max cannot return 0 as an estimate of the number of retrieved records. Yet the function erroneously returned 0 as the estimate in some situations.
-
pem@mysql.com authored
into mysql.com:/extern/mysql/work/bug16303/mysql-5.0
-
pem@mysql.com authored
into mysql.com:/extern/mysql/work/bug16303/mysql-5.0
-
pem@mysql.com authored
-
pem@mysql.com authored
into mysql.com:/extern/mysql/work/bug16568/mysql-5.0
-
- 05 Feb, 2006 3 commits
-
-
pekka@mysql.com authored
-
pekka@mysql.com authored
into mysql.com:/space/pekka/ndb/version/my50
-
pekka@mysql.com authored
-
- 03 Feb, 2006 9 commits
-
-
pekka@mysql.com authored
into mysql.com:/space/pekka/ndb/version/my50
-
pekka@mysql.com authored
-
pekka@mysql.com authored
-
igor@rurik.mysql.com authored
into rurik.mysql.com:/home/igor/dev/mysql-5.0-0
-
igor@rurik.mysql.com authored
-
igor@rurik.mysql.com authored
into rurik.mysql.com:/home/igor/dev/mysql-5.0-0
-
igor@rurik.mysql.com authored
-
igor@rurik.mysql.com authored
into rurik.mysql.com:/home/igor/dev/mysql-4.1-0
-
igor@rurik.mysql.com authored
into rurik.mysql.com:/home/igor/mysql-5.0
-
- 02 Feb, 2006 12 commits
-
-
konstantin@mysql.com authored
-
igor@rurik.mysql.com authored
into rurik.mysql.com:/home/igor/dev/mysql-5.0-0
-
konstantin@mysql.com authored
-
konstantin@mysql.com authored
into mysql.com:/opt/local/work/mysql-5.0-root
-
gunnar@mysql.com. authored
manual adding the fix for bug#15828 which did not automerge
-
gunnar@mysql.com. authored
into mysql.com.:/data/BK/mysql-5.0_15828
-
konstantin@mysql.com authored
into mysql.com:/opt/local/work/mysql-5.0-root
-
pem@mysql.com authored
(No change of functionality)
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/mysql-5.0
-
msvensson@neptunus.(none) authored
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/mysql-5.0
-
igor@rurik.mysql.com authored
When an ambiguous field name is used in a group by clause a warning is issued in the find_order_in_list function by a call to push_warning_printf. An expression that was not always valid was passed to this call as the field name parameter.
-
- 01 Feb, 2006 8 commits
-
-
andrey@lmy004. authored
-
pem@mysql.com authored
into mysql.com:/extern/mysql/work/bug15011/mysql-5.0
-
pem@mysql.com authored
Added comments.
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/mysql-5.0
-
pem@mysql.com authored
which is no longer repeatable. (Unclear when this was fixed.)
-
pem@mysql.com authored
into mysql.com:/extern/mysql/work/cantrepeat/mysql-5.0
-
msvensson@neptunus.(none) authored
Fix for extra zero in exponent of double values on windows.
-
igor@rurik.mysql.com authored
A query with a group by and having clauses could return a wrong result set if the having condition contained a constant conjunct evaluated to FALSE. It happened because the pushdown condition for table with grouping columns lost its constant conjuncts. Pushdown conditions are always built by the function make_cond_for_table that ignores constant conjuncts. This is apparently not correct when constant false conjuncts are present.
-