- 30 Oct, 2007 2 commits
-
-
df@pippilotta.erinye.com authored
into pippilotta.erinye.com:/shared/home/df/mysql/build/mysql-5.1-build-work
-
df@pippilotta.erinye.com authored
-
- 25 Oct, 2007 2 commits
-
-
df@pippilotta.erinye.com authored
into pippilotta.erinye.com:/shared/home/df/mysql/build/mysql-5.0-build
-
df@pippilotta.erinye.com authored
-
- 22 Oct, 2007 4 commits
-
-
mleich@four.local.lan authored
- Fix for Bug#28827 Partition test needs archive engine Bug#26669 Two tests on partition fail while blackhole engine is missing Solution: Move ARCHIVE and BLACKHOLE sub test cases to their own main test. - The two bugs above + the fact that CSV could be also sometimes not available --> Move also CSV sub tests out. - Minor cleanups - Replace error numbers with error names - fix typos, wrong comments - remove redundant sub test cases - add missing drop database - SET GLOBAL general_log = default is wrong, = 1 is correct
-
joerg@trift2. authored
into trift2.:/MySQL/M51/push-5.1
-
joerg@trift2. authored
into trift2.:/MySQL/M51/push-5.1
-
joerg@trift2. authored
into trift2.:/MySQL/M50/push-5.0
-
- 19 Oct, 2007 9 commits
-
-
joerg@trift2. authored
into trift2.:/MySQL/M51/push-5.1
-
joerg@trift2. authored
into trift2.:/MySQL/M51/push-5.1
-
joerg@trift2. authored
into trift2.:/MySQL/M50/push-5.0
-
joerg@trift2. authored
into trift2.:/MySQL/M51/bug31644-5.1
-
joerg@trift2. authored
into trift2.:/MySQL/M51/push-5.1
-
joerg@trift2. authored
into trift2.:/MySQL/M51/push-5.1
-
joerg@trift2. authored
into trift2.:/MySQL/M50/push-5.0
-
malff@lambda.hsd1.co.comcast.net. authored
into lambda.hsd1.co.comcast.net.:/home/malff/TREE/mysql-5.1-runtime
-
malff@lambda.hsd1.co.comcast.net. authored
into lambda.hsd1.co.comcast.net.:/home/malff/TREE/mysql-5.1-rt-merge
-
- 18 Oct, 2007 10 commits
-
-
malff@lambda.hsd1.co.comcast.net. authored
into lambda.hsd1.co.comcast.net.:/home/malff/TREE/mysql-5.1-rt-merge
-
malff@lambda.hsd1.co.comcast.net. authored
into lambda.hsd1.co.comcast.net.:/home/malff/TREE/mysql-5.0-rt-merge
-
davi@moksha.com.br authored
into moksha.com.br:/Users/davi/mysql/mysql-5.1-runtime
-
davi@moksha.com.br authored
-
davi@moksha.com.br authored
into moksha.com.br:/Users/davi/mysql/mysql-5.1-runtime
-
davi@moksha.com.br authored
The general log write function (general_log_print) uses printf style arguments which need to be pre-processed, meaning that the all arguments are copied to a single buffer and the problem is that the buffer size is constant (1022 characters) but queries can be much larger then this. The solution is to introduce a new log write function that accepts a buffer and it's length as arguments. The function is to be used when a formatted output is not required, which is the case for almost all query write-to-log calls. This is a incompatible change with respect to the log format of prepared statements.
-
mleich@four.local.lan authored
into four.local.lan:/WORK/mysql-5.1-build/src-clean
-
mleich@four.local.lan authored
into four.local.lan:/WORK2/merge/mysql-5.1-31556
-
mleich@four.local.lan authored
Bug#31556 Test failure: "select hex(ascii(a)) ... order by a" results in different order
-
joerg@trift2. authored
and the modified values of the compile-related variables used in "configure". Make the necessary adjustments in "configure.in" and "scripts/Makefile.am". This fixes bug#31644 Values of *FLAGS that were used for building packages is missed in mysqlbug
-
- 17 Oct, 2007 13 commits
-
-
dkatz@damien-katzs-computer.local authored
into damien-katzs-computer.local:/Users/dkatz/mysql-5.1-runtime
-
dkatz@damien-katzs-computer.local authored
Previously, UDF *_init functions were passed constant strings with erroneous lengths. The length came from the containing variable's size, not the length of the value itself. Now the *_init functions get the constant as a null terminated string with the correct length supplied too.
-
davi@moksha.com.br authored
into moksha.com.br:/Users/davi/mysql/mysql-5.1-runtime
-
davi@moksha.com.br authored
Post merge fixes: close any open statement before the change user command and fix test case output.
-
tsmith@ramayana.hindu.god authored
into ramayana.hindu.god:/home/tsmith/m/bk/maint/51
-
tsmith@ramayana.hindu.god authored
in middle of block)
-
davi@moksha.com.br authored
into moksha.com.br:/Users/davi/mysql/mysql-5.1-runtime
-
anozdrin/alik@station. authored
-
anozdrin/alik@station. authored
The problem was that the RETURNS column in the mysql.proc was of CHAR(64). That was not enough for storing long-named datatypes. The fix is to change CHAR(64) to LONGBLOB, and to throw warnings at the time a stored routine is created if some data is truncated during writing into mysql.proc.
-
kaa@polly.(none) authored
into polly.(none):/home/kaa/src/maint/mysql-5.1-maint
-
kaa@polly.(none) authored
into polly.(none):/home/kaa/src/maint/mysql-5.0-maint
-
kaa@polly.(none) authored
-
malff@lambda.hsd1.co.comcast.net. authored
-