- 03 Dec, 2003 4 commits
-
-
paul@ice.snake.net authored
into ice.snake.net:/Volumes/ice2/MySQL/bk/mysql-4.1
-
paul@ice.snake.net authored
-
lenz@mysql.com authored
into mysql.com:/space/my/mysql-4.1
-
paul@ice.snake.net authored
-
- 02 Dec, 2003 8 commits
-
-
-
-
konstantin@mysql.com authored
into mysql.com:/home/kostja/mysql/mysql-4.1-root
-
hf@deer.(none) authored
Second edition: error message was deleted as Segey suggested Now name of the constraint will be used as the name of the key if the last not specified
-
lenz@kallisto.local authored
added to manual.texi - extract it from there instead.
-
konstantin@oak.local authored
thd->command can be anything except COM_EXECUTE in no cases except programming error.
-
monty@mysql.com authored
Ensure that innodb is created for the first replication test as the slave-timeout is lower for future tests and this failed on some slower machines
-
konstantin@mysql.com authored
into mysql.com:/home/kostja/mysql/mysql-4.1-root
-
- 01 Dec, 2003 5 commits
-
-
igor@rurik.mysql.com authored
Fixed inconsistency of values of used_tables_cache and const_item_cache for Item_func_isnull objects (bug #1990).
-
konstantin@oak.local authored
followup of Bordeaux Optimizer session
-
konstantin@mysql.com authored
into mysql.com:/home/kostja/mysql/mysql-4.1-root
-
konstantin@oak.local authored
all items in free_prep_stmt(free_items); indentation fix
-
monty@mysql.com authored
Added --protocol to mysqlbinlog
-
- 28 Nov, 2003 23 commits
-
-
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
-