- 30 Aug, 2006 2 commits
-
-
into mysql.com:/Users/kent/mysql/bk/mysql-5.0
-
Auto merged
-
- 29 Aug, 2006 1 commit
-
-
into mysql.com:/Users/kent/mysql/bk/mysql-5.0
-
- 28 Aug, 2006 1 commit
-
-
timour/tkatchaounov@dl145s.mysql.com authored
into dl145s.mysql.com:/data/tkatchaounov/autopush/5.0-bug-21456
-
- 26 Aug, 2006 3 commits
-
-
evgen@moonbone.local authored
into moonbone.local:/work/tmp_merge-5.0-mysql
-
evgen@moonbone.local authored
into moonbone.local:/work/tmp_merge-4.1-opt-mysql
-
evgen@moonbone.local authored
into moonbone.local:/work/tmp_merge-5.0-mysql
-
- 25 Aug, 2006 5 commits
-
-
cmiller@zippy.cornsilk.net authored
into zippy.cornsilk.net:/home/cmiller/work/mysql/release/mysql-5.0-release
-
cmiller@zippy.cornsilk.net authored
InterfaceError on connect Removed the bool flag from the st_mysql_options struct, since it adds another word in size to the memory size and shifts member memory locations down, both of which break binary-interface compatibility. Instead, use a flag, 2**30, in the client_options bit-field to represent that the client should check the SSL certificate of the server.
-
sergefp@mysql.com authored
into mysql.com:/home/psergey/mysql-5.0-bug16255-merge
-
igor@rurik.mysql.com authored
into rurik.mysql.com:/home/igor/mysql-5.0-opt
-
igor@rurik.mysql.com authored
const tables. This resulted in choosing extremely inefficient execution plans in same cases when distribution of data in joined were skewed (see the customer test case for the bug).
-
- 24 Aug, 2006 6 commits
-
-
evgen@sunlight.local authored
Corrected fix for bug#18165
-
evgen@moonbone.local authored
Corrected fix for bug#18165
-
sergefp@mysql.com authored
-
sergefp@mysql.com authored
-
sergefp@mysql.com authored
Must not use Item_direct_ref in HAVING because it points to the new value (witch is not yet calculated for the first row).
-
anozdrin/alik@alik. authored
User name (host name) has limit on length. The server code relies on these limits when storing the names. The problem was that sometimes these limits were not checked properly, so that could lead to buffer overflow. The fix is to check length of user/host name in parser and if string is too long, throw an error.
-
- 23 Aug, 2006 5 commits
-
-
evgen@sunlight.local authored
Corrected test case for the bug#21261 sql_parse.cc: Corrected fix for bug#21261
-
joerg@trift2. authored
-
timour/timka@lamia.home authored
into lamia.home:/home/timka/mysql/src/5.0-bug-21456
-
timour/timka@lamia.home authored
GROUP BY/DISTINCT pruning optimization must be done before ORDER BY optimization because ORDER BY may be removed when GROUP BY/DISTINCT sorts as a side effect, e.g. in SELECT DISTINCT <non-key-col>,<pk> FROM t1 ORDER BY <non-key-col> DISTINCT must be removed before ORDER BY as if done the other way around it will remove both.
-
joerg@trift2. authored
These variables must be defined for Netware, or it fails to recognize hard paths starting from the device. (Packport of: 2006/08/16 19:30:46+03:00 jani@ua141d10.elisa.omakaista.fi )
-
- 22 Aug, 2006 15 commits
-
-
evgen@moonbone.local authored
into moonbone.local:/work/21475-fix-5.0-opt-mysql
-
evgen@moonbone.local authored
Additional fix for bug #21475 item_func.h, item_func.cc: Additional fix for bug#16861
-
into salvation.intern.azundris.com:/home/tnurnberg/work/mysql-5.0-maint-20987
-
into salvation.intern.azundris.com:/home/tnurnberg/work/mysql-5.0-maint-20987
-
cmiller@zippy.cornsilk.net authored
into zippy.cornsilk.net:/home/cmiller/work/mysql/merge/mysql-5.0
-
igor@rurik.mysql.com authored
into rurik.mysql.com:/home/igor/mysql-5.0-opt
-
evgen@sunlight.local authored
into sunlight.local:/local_work/16861-bug-5.0-mysql
-
evgen@sunlight.local authored
used. Sorting by RAND() uses a temporary table in order to get a correct results. User defined variable was set during filling the temporary table and later on it is substituted for its value from the temporary table. Due to this it contains the last value stored in the temporary table. Now if the result_field is set for the Item_func_set_user_var object it updates variable from the result_field value when being sent to a client. The Item_func_set_user_var::check() now accepts a use_result_field parameter. Depending on its value the result_field or the args[0] is used to get current value.
-
evgen@moonbone.local authored
into moonbone.local:/work/21475-bug-5.0-opt-mysql
-
into salvation.intern.azundris.com:/home/tnurnberg/work/mysql-5.0-maint-20411
-
when X.509 subject was required for a connect, we tested whether it was the right one, but did not refuse the connexion if not. fixed. (corrected CS now --replace_results socket-path)
-
into salvation.intern.azundris.com:/home/tnurnberg/work/mysql-5.0-maint-20987
-
igor@rurik.mysql.com authored
buffer for a MY_BITMAP temporary buffer allocated on stack in the function get_best_covering_ror_intersect(). Now the buffer of a proper size is allocated by a request from this function in mem_root. We succeeded to demonstrate the bug only on Windows with a very large database. That's why no test case is provided for in the patch.
-
sergefp@mysql.com authored
-
iggy@rolltop.ignatz42.dyndns.org authored
-
- 21 Aug, 2006 2 commits
-
-
sergefp@mysql.com authored
-
msvensson@shellback.(none) authored
into shellback.(none):/home/msvensson/mysql/mysql-5.0-maint
-