- 03 Dec, 2003 1 commit
-
-
igor@rurik.mysql.com authored
after introducing Item_equal.
-
- 02 Dec, 2003 6 commits
-
-
igor@rurik.mysql.com authored
Fixed a problem a with special cases of IS NULL usage caused by some erroneous change made when Item_equal was introduced.
-
igor@rurik.mysql.com authored
-
igor@rurik.mysql.com authored
Added tests for != predicate. sql_select.cc: Fixing bugs in Item_equal code: added a parameter in substitute_for_equal_field; modified eliminate_item_equal. sql_list.h: Cleanup
-
igor@rurik.mysql.com authored
into rurik.mysql.com:/home/igor/dev/mysql-5.0-1
-
igor@rurik.mysql.com authored
Fixed inconsistency of values of used_tables_cache and const_item_cache for Item_func_isnull objects (bug #1990).
-
igor@rurik.mysql.com authored
Fixed inconsistency of values of used_tables_cache and const_item_cache for Item_func_isnull objects (bug #1990). item_cmpfunc.h: Fixed inconsistency of values of used_tables_cache and const_item_cache for Item_func_isnull objects (bug #1990).
-
- 01 Dec, 2003 3 commits
-
-
pem@mysql.comhem.se authored
-
pem@mysql.com authored
-
monty@mysql.com authored
Added --protocol to mysqlbinlog
-
- 28 Nov, 2003 26 commits
-
-
igor@rurik.mysql.com authored
into rurik.mysql.com:/home/igor/dev/mysql-5.0-0
-
monty@mysql.com authored
-
monty@mysql.com authored
-
monty@mysql.com authored
-
monty@mysql.com authored
into mysql.com:/my/mysql-4.1
-
serg@serg.mylan authored
into serg.mylan:/usr/home/serg/Abk/mysql-4.0
-
serg@serg.mylan authored
It happens that mysql->client_next->client_next=mysql and mysql_close() goes into infinite loop. Results vary from simple sigsegv (FreeBSD), to hard system lockup (Linux) :)
-
guilhem@mysql.com authored
into mysql.com:/home/mysql_src/mysql-4.1
-
guilhem@mysql.com authored
the relay log before flushing master.info. Doing 'before' leads to duplicate event, doing after leads to missing event. Both can be as destructive, but 'duplicate' enables us to later add detection code to catch it. Whereas 'missing' can't be caught (it can't, because the I/O thread can produce legal position jumps, for example if it has ignored an event coming from this slave (rememember that starting from 4.1.1, the I/O thread filters the server id).
-
konstantin@mysql.com authored
into mysql.com:/home/kostja/mysql/mysql-4.1-root
-
konstantin@oak.local authored
-
monty@mysql.com authored
-
monty@mysql.com authored
into mysql.com:/my/mysql-4.0
-
monty@mysql.com authored
-
monty@mysql.com authored
into mysql.com:/my/mysql-4.1
-
monty@mysql.com authored
into mysql.com:/my/mysql-4.1
-
serg@serg.mylan authored
into serg.mylan:/usr/home/serg/Abk/mysql-4.0
-
serg@serg.mylan authored
into serg.mylan:/usr/home/serg/Abk/mysql-4.1
-
serg@serg.mylan authored
-
serg@serg.mylan authored
-
monty@mysql.com authored
-
monty@mysql.com authored
-
monty@mysql.com authored
Fixed compiler warnings (a lot of hidden variables detected by the Forte compiler) Added a lot of 'version_xxx' strings to 'show variables' Prevent copying of TMP_TABLE_PARAM (This caused core dump bug on Solaris) Fixed problem with printing sub selects to debug log
-
konstantin@oak.local authored
-
konstantin@mysql.com authored
into mysql.com:/home/kostja/mysql/mysql-4.1-wl519
-
konstantin@oak.local authored
Client option secure-auth deployed on all possible layers: - mysql client command-line and config file option - mysql_options option MYSQL_SECURE_AUTH - mysql_real_connect will automatically take into account that option if mysql->options.my_cnf_file/my_cnf_group is set
-
- 27 Nov, 2003 4 commits
-
-
konstantin@oak.local authored
2 forgotten 'break;' statements added
-
konstantin@mysql.com authored
into mysql.com:/home/kostja/mysql/mysql-4.0-root
-
konstantin@mysql.com authored
options.rpl_probe} as they are zero-initialized in spawn_init()
-
konstantin@mysql.com authored
no need to set rpl_parse, rpl_probe and rpl_pivot to zero as whole mysql structure is bzeroed in mysql_init(0) few lines before
-