- 19 Jul, 2005 23 commits
-
-
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-4.1-clean
-
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
-
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.
-
elliot@mysql.com authored
into mysql.com:/Users/emurphy/src/work/mysql-5.0-bug11567
-
patg@radha.local authored
into radha.local:/Users/patg/mysql-build/mysql-5.0
-
jimw@mysql.com authored
into mysql.com:/home/jimw/my/mysql-5.0-readline
-
patg@radha.local authored
as well as changes to the test.
-
jimw@mysql.com authored
-
jimw@mysql.com authored
-
- 18 Jul, 2005 17 commits
-
-
konstantin@mysql.com authored
-
elliot@mysql.com authored
into mysql.com:/Users/emurphy/src/work/mysql-5.0-bug11567
-
elliot@mysql.com authored
-
konstantin@mysql.com authored
into mysql.com:/home/kostja/mysql/mysql-5.0-merge
-
shuichi@mysql.com authored
-
konstantin@mysql.com authored
-
monty@mishka.local authored
get_defaults_file() -> get_defaults_options()
-
monty@mishka.local authored
into mishka.local:/home/my/mysql-5.0
-
evgen@moonbone.local authored
into moonbone.local:/work/mysql-5.0-bug-11482
-
evgen@moonbone.local authored
into moonbone.local:/work/mysql-5.0-bug-11482
-
georg@lmy002.wdf.sap.corp authored
into lmy002.wdf.sap.corp:/home/georg/work/mysql/prod/mysql-5.0
-
evgen@moonbone.local authored
Changed test case comment to be more meaningful
-
evgen@moonbone.local authored
-
evgen@moonbone.local authored
than in previous 4.1.x Wrongly applied optimization were adding NOT NULL constraint which results in rejecting valid rows and reduced result set. The problem was that add_notnull_conds() while checking subquery were adding NOT NULL constraint to left joined table, to which, normally, optimization don't have to be applied.
-
reggie@linux.site authored
into linux.site:/home/reggie/bk/bug7142
-
konstantin@mysql.com authored
-
gbichot@production.mysql.com authored
into production.mysql.com:/nfstmp1/guilhem/mysql-4.1-prod
-