- 20 Jul, 2005 8 commits
-
-
stewart@mysql.com authored
into mysql.com:/home/stewart/Documents/MySQL/5.0/main
-
jimw@mysql.com authored
-
jimw@mysql.com authored
into mysql.com:/home/jimw/my/mysql-5.0-clean
-
jimw@mysql.com authored
into mysql.com:/home/jimw/my/mysql-5.0-clean
-
jimw@mysql.com authored
into mysql.com:/home/jimw/my/mysql-5.0-clean
-
jimw@mysql.com authored
into mysql.com:/home/jimw/my/mysql-5.0-clean
-
evgen@moonbone.local authored
into moonbone.local:/work/mysql-5.0-bug-11760
-
evgen@moonbone.local authored
by subtime() in view Item_func_add_time::print() were printing arg[0] instead of arg[1] which results in wrongly created view. Functions addtime() and subtime were affected by this bug.
-
- 19 Jul, 2005 32 commits
-
-
jimw@mysql.com authored
-
konstantin@mysql.com authored
-
elliot@mysql.com authored
into mysql.com:/data0/emurphy/src/mysql-5.0
-
elliot@mysql.com authored
BUG#12040 Fixed compile failure by using %p instead of %x to print a pointer in DBUG_PRINT
-
konstantin@mysql.com authored
-
konstantin@mysql.com authored
Delete: mysql-test/var
-
konstantin@mysql.com authored
into mysql.com:/home/kostja/mysql/mysql-5.0-10760-new
-
konstantin@mysql.com authored
The idea of the patch is that every cursor gets its own lock id for table level locking. Thus cursors are protected from updates performed within the same connection. Additionally a list of transient (must be closed at commit) cursors is maintained and all transient cursors are closed when necessary. Lastly, this patch adds support for deadlock timeouts to TLL locking when using cursors. + post-review fixes.
-
jimw@mysql.com authored
into mysql.com:/home/jimw/my/mysql-5.0-clean
-
dlenev@mysql.com authored
into mysql.com:/home/dlenev/src/mysql-5.0-tn
-
dlenev@mysql.com authored
-
jimw@mysql.com authored
into mysql.com:/home/jimw/my/mysql-4.1-clean
-
dlenev@mysql.com authored
into mysql.com:/home/dlenev/src/mysql-5.0-tn
-
monty@mishka.local authored
-
monty@mishka.local authored
into mishka.local:/home/my/mysql-4.1
-
monty@mishka.local authored
-
jimw@mysql.com authored
into mysql.com:/home/jimw/my/mysql-5.0-clean
-
dlenev@mysql.com authored
"Triggers have the wrong namespace" "Triggers: duplicate names allowed" "Triggers: CREATE TRIGGER does not accept fully qualified names" "SHOW TRIGGERS"
-
tulin@dl145b.mysql.com authored
-
tulin@dl145b.mysql.com authored
BUG#12028, cannot use default section for hostname in cluster config made clearer error message
-
tulin@dl145b.mysql.com authored
+ added switch --print-full-config + removed unused REP configuration
-
ingo@mysql.com authored
This patch allows to configure MyISAM for 128 indexes per table. The main problem is the key_map, wich is implemented as an ulonglong. To get rid of the limit and keep the efficient and flexible implementation, the highest bit is now used for all upper keys. This means that the lower keys can be disabled and enabled individually as usual and the high keys can only be disabled and enabled as a block. That way the existing test suite is still applicable, while more keys work, though slightly less efficient. To really get more than 64 keys, some defines need to be changed. Another patch will address this.
-
tulin@dl145b.mysql.com authored
BUG#11999, incorrect --help on perror with ndb
-
gluh@eagle.intranet.mysql.r18.ru authored
fixed BLOB, TEXT(wrong maximum length), BIT and integer types(wrong numeric_precision value)
-
gluh@mysql.com authored
into mysql.com:/home/gluh/MySQL/Merge/5.0
-
gluh@eagle.intranet.mysql.r18.ru authored
changed 'SHOW PROCEDURE' behavoiur to be like INFORMATION_SCHEMA.routines
-
konstantin@mysql.com authored
-
konstantin@mysql.com authored
list.
-
stewart@mysql.com authored
into mysql.com:/home/stewart/Documents/MySQL/5.0/main
-
elliot@mysql.com authored
into mysql.com:/Users/emurphy/src/work/mysql-5.0-bug11567
-
jimw@mysql.com authored
by mysql-test-run.pl. (Bug #11954)
-
patg@radha.local authored
into radha.local:/Users/patg/mysql-build/mysql-5.0
-