- 19 Jul, 2005 21 commits
-
-
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
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.
-
dlenev@mysql.com authored
into mysql.com:/home/dlenev/src/mysql-5.0-tn
-
dlenev@mysql.com authored
-
dlenev@mysql.com authored
into mysql.com:/home/dlenev/src/mysql-5.0-tn
-
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"
-
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.
-
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 19 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.
-
konstantin@mysql.com authored
-
gbichot@production.mysql.com authored
into production.mysql.com:/nfstmp1/guilhem/mysql-4.1-prod
-
gbichot@production.mysql.com authored
LOCK_thread_count)" and for BUG#12004 "SHOW BINARY LOGS reports 0 for the size of all binlogs but the current one". There are a lot of 4.1->5.0 unmerged changes (hardest are in the optimizer), can't merge; still pushing in 4.1 because my changes are very small. Feel free to ask me if you have problems merging them.
-
monty@mishka.local authored
Changed defaults option --instance to --defaults-group-suffix Changed option handling to allow --defaults-file, --defaults-extra-file and --defaults-group-suffix to be given in any order Changed MYSQL_INSTANCE to MYSQL_GROUP_SUFFIX mysql_print_defaults now understands --defaults-group-suffix Remove usage of my_tempnam() (not safe function) if( -> if ( and while( to while (
-
joerg@mysql.com authored
-