- 29 Mar, 2005 2 commits
-
-
monty@mysql.com authored
into mysql.com:/home/my/mysql-5.0
-
monty@mysql.com authored
-
- 28 Mar, 2005 14 commits
-
-
pekka@mysql.com authored
-
pekka@mysql.com authored
into mysql.com:/space/pekka/ndb/version/my41
-
pekka@mysql.com authored
-
serg@serg.mylan authored
into serg.mylan:/usr/home/serg/Abk/mysql-4.1
-
pekka@mysql.com authored
into mysql.com:/export/space/pekka/ndb/version/my50
-
pekka@mysql.com authored
-
bar@eagle.intranet.mysql.r18.ru authored
into eagle.intranet.mysql.r18.ru:/home/bar/mysql-5.0
-
bar@mysql.com authored
Bug #6519 UNION with collation binary and latin1_swedish_ci fails now Prove that this problem was fixed with bug9425 fix too.
-
bar@eagle.intranet.mysql.r18.ru authored
Post merge additional fix for DECIMAL type: Bugs: #9425: A user variable doesn't always have implicit coercibility
-
bar@eagle.intranet.mysql.r18.ru authored
into eagle.intranet.mysql.r18.ru:/home/bar/mysql-5.0
-
bar@mysql.com authored
Coercibility fixes for numeric types and not defined values were done.
-
serg@serg.mylan authored
into serg.mylan:/usr/home/serg/Abk/mysql-4.1
-
bar@eagle.intranet.mysql.r18.ru authored
into eagle.intranet.mysql.r18.ru:/home/bar/mysql-5.0
-
bar@mysql.com authored
Prove that the queries mentioned in Bugs#5980: NULL requires a characterset in a union works fine after recent changes related to itroducing more coercibility level: IRNORABLE and SYSCONST.
-
- 27 Mar, 2005 1 commit
-
-
serg@serg.mylan authored
-
- 26 Mar, 2005 5 commits
-
-
serg@serg.mylan authored
-
serg@serg.mylan authored
into serg.mylan:/usr/home/serg/Abk/mysql-4.1
-
serg@serg.mylan authored
into serg.mylan:/usr/home/serg/Abk/mysql-4.0
-
serg@serg.mylan authored
-
gbichot@quadita2.mysql.com authored
into quadita2.mysql.com:/nfstmp1/guilhem/mysql-5.0-4ita
-
- 25 Mar, 2005 18 commits
-
-
konstantin@mysql.com authored
-
konstantin@mysql.com authored
provide created shared memory objects with proper access rights to make them usable when client and server are running under different accounts. Post review fixes.
-
brian@zim.(none) authored
-
brian@zim.(none) authored
-
brian@zim.(none) authored
-
brian@zim.(none) authored
-
brian@zim.(none) authored
into zim.(none):/home/brian/mysql/mysql-5.0
-
brian@zim.(none) authored
-
brian@zim.(none) authored
into zim.(none):/home/brian/mysql/mysql-4.1
-
jimw@mysql.com authored
into mysql.com:/home/jimw/my/mysql-5.0-clean
-
brian@zim.(none) authored
-
jimw@mysql.com authored
into mysql.com:/home/jimw/my/mysql-4.1-clean
-
jimw@mysql.com authored
into mysql.com:/home/jimw/my/mysql-4.1-clean
-
jimw@mysql.com authored
into mysql.com:/home/jimw/my/mysql-5.0-clean
-
gbichot@quadita2.mysql.com authored
into quadita2.mysql.com:/nfstmp1/guilhem/mysql-5.0-4ita
-
gbichot@quadita2.mysql.com authored
This saves one byte per Query_log_event on disk compared to 5.0.[0..3]. Compatibility problems with 5.0.x where x<4 are explained in the comments in log_event.cc. Putting back s/my_open(O_TRUNC)/(my_delete+my_create) change which had been wiped away by somebody doing a wrong 4.1->5.0 merge (which happened just before 5.0.3 :( ). Applying it to new events for LOAD DATA INFILE. If slave fails in Execute_load_query_log_event::exec_event(), don't delete the file (so that it's re-usable at next START SLAVE). And (youpi!) fix for BUG#3247 "a partially completed LOAD DATA INFILE is not executed at all on the slave" (storing an Execute_load_query_log_event to binlog, with its error code, instead of Delete_file_log_event).
-
bar@eagle.intranet.mysql.r18.ru authored
into eagle.intranet.mysql.r18.ru:/home/bar/mysql-5.0
-
bar@mysql.com authored
Don't run GBK test if not GBK support was compiled.
-