- 31 Jul, 2006 1 commit
-
-
into mysql.com:/users/lthalmann/bk/MERGE/mysql-5.0-merge
-
- 28 Jul, 2006 1 commit
-
-
- 27 Jul, 2006 1 commit
-
-
- 26 Jul, 2006 3 commits
-
-
aivanov@mysql.com authored
-
aivanov@mysql.com authored
into mysql.com:/home/alexi/innodb/mysql-5.0-work Null merge.
-
aivanov@mysql.com authored
-
- 18 Jul, 2006 4 commits
-
-
into production.mysql.com:/usersnfs/abotchkov/mysql-5.0.mrg
-
holyfoot/hf@mysql.com/deer.(none) authored
-
holyfoot/hf@mysql.com/deer.(none) authored
into mysql.com:/home/hf/work/mysql-5.0.mrg
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/mysql-5.0
-
- 17 Jul, 2006 2 commits
-
-
msvensson@shellback.(none) authored
into shellback.(none):/home/msvensson/mysql/mysql-5.0-maint
-
msvensson@shellback.(none) authored
- Fix for "bug#16755 Please find a SSL library that is FLOSS-Exception / LGPL copyrighted"
-
- 15 Jul, 2006 1 commit
-
-
pekka@orca.ndb.mysql.com authored
into orca.ndb.mysql.com:/space_old/pekka/ndb/version/my50
-
- 14 Jul, 2006 3 commits
-
-
-
into anubis.greendragongames.com:/home/greenman/workspace-mysql/mysql/merge-4.1_2_5.0
-
-
- 13 Jul, 2006 13 commits
-
-
-
into mysql.com:/home/tnurnberg/work/mysql-5.0-21014
-
mysqldump did not select the correct database before trying to dump views from it. this resulted in an empty result set, which in turn startled mysql-dump into a core-dump. this only happened for views, not for tables, and was only visible with multiple databases that weren't by sheer luck in the order mysqldump required, anyway. this fixes by selecting the correct database before dumping views; it also catches the empty set-condition if it should occur for other reasons.
-
holyfoot/hf@mysql.com/deer.(none) authored
into mysql.com:/home/hf/work/mysql-4.1.16017
-
cmiller@zippy.(none) authored
into zippy.(none):/home/cmiller/work/mysql/m41-maint--07AB5
-
cmiller@zippy.(none) authored
into zippy.(none):/home/cmiller/work/mysql/m41-maint--07AB5
-
cmiller@zippy.(none) authored
into zippy.(none):/home/cmiller/work/mysql/m50--07C2P
-
cmiller@zippy.(none) authored
into zippy.(none):/home/cmiller/work/mysql/m50-maint--07C2P
-
cmiller@zippy.(none) authored
into zippy.(none):/home/cmiller/work/mysql/m50-maint--07C2P
-
iggy@rolltop.ignatz42.dyndns.org authored
-
holyfoot/hf@mysql.com/deer.(none) authored
into mysql.com:/home/hf/work/mysql-5.0.clean
-
into anubis.greendragongames.com:/home/greenman/workspace-mysql/mysql/pending/bug-4.1-15977
-
do not look for client-specific commands while inside a multi-line comment. we will allow multi-comments pretty much anywhere within SQL-statements, but client-specific commands (help, use, print, ...) must be the first token in the input.
-
- 12 Jul, 2006 6 commits
-
-
cmiller@zippy.(none) authored
into zippy.(none):/home/cmiller/work/mysql/m50-maint--07C2P
-
kostja@bodhi.local authored
-
cmiller@calliope.local authored
The bug is thqt we use some nonstandard assembly codes in our strings source, and some assemblers don't know what to do with them: Specifically, Sun's Solaris assembler and Apple's Darwin assembler balk at them. This patch, rather than trying to test for properties of the assembler, which Autoconf doesn't have any decent facilites for, instead tries to compile the code in question and disables assembly if it fails. There's still the problem of unportable assembly, but I'll leave that to someone who feels like rewriting and debugging it.
-
mkindahl@dl145k.mysql.com authored
into dl145k.mysql.com:/data0/mkindahl/bk/mysql-5.0-rpl
-
mkindahl@dl145k.mysql.com authored
into dl145k.mysql.com:/data0/mkindahl/bk/mysql-4.1-rpl
-
cmiller@maint1.mysql.com authored
into maint1.mysql.com:/data/localhome/cmiller/mysql-4.1
-
- 11 Jul, 2006 5 commits
-
-
cmiller@zippy.(none) authored
into zippy.(none):/home/cmiller/work/mysql/m41-maint--07AB5
-
cmiller@zippy.(none) authored
The problem is that the author used the wrong function to send a warning to the user about truncation of data. push_warning() takes a constant string and push_warning_printf() takes a format and variable arguments to fill it. Since the string we were complaining about contains percent characters, the printf() code interprets the "%Y" et c. that the user sends. That's wrong, and often causes a crash, especially if the date mentions seconds, "%s". A alternate fix would be to use push_warning_printf(..., "%s", warn_buff) .
-
pekka@orca.ndb.mysql.com authored
-
kostja@bodhi.local authored
into bodhi.local:/opt/local/work/mysql-5.0-runtime-merge-41
-
cmiller@zippy.(none) authored
into zippy.(none):/home/cmiller/work/mysql/merge/mysql-4.1
-