- 25 Oct, 2007 1 commit
-
-
svoj@june.mysql.com authored
into mysql.com:/home/svoj/devel/mysql/BUG31159/mysql-5.1-engines
-
- 24 Oct, 2007 3 commits
-
-
svoj@june.mysql.com authored
into mysql.com:/home/svoj/devel/mysql/BUG31159/mysql-5.0-engines
-
svoj@mysql.com/june.mysql.com authored
into mysql.com:/home/svoj/devel/mysql/BUG31159/mysql-4.1-engines
-
svoj@mysql.com/june.mysql.com authored
ucs2 doesn't provide required by fulltext ctype array. Crash happens because fulltext attempts to use unitialized ctype array. Fixed by converting ucs2 fields to compatible utf8 analogue.
-
- 23 Oct, 2007 3 commits
-
-
mattiasj@mattiasj-laptop.(none) authored
into mattiasj-laptop.(none):/home/mattiasj/clones/mysql-5.1-bug30878
-
mattiasj@mattiasj-laptop.(none) authored
into mattiasj-laptop.(none):/home/mattiasj/clones/mysql-5.1-bug30878
-
mattiasj@mattiasj-laptop.(none) authored
causes the Server to crash. Accessing partitioned table with an apostrophe in partition options like DATA DIRECTORY, INDEX DIRECTORY or COMMENT causes server crash. Partition options were saved in .frm file without escaping. When accessing such table it is not possible to properly restore partition information. Crashed because there was no check for partition info parser failure. Fixed by escaping quoted text in the partition info when writing it to the frm-file and added a check that it was able to parse the partition info before using it NOTE: If the comment is written by an earlier version of the server, the corrupted frm-file is not fixed, but left corrupted, you have to manually drop the table and recreate it.
-
- 19 Oct, 2007 7 commits
-
-
antony@anubis.xiphis.org authored
into anubis.xiphis.org:/usr/home/antony/work/mysql-5.1-engines.merge
-
antony@anubis.xiphis.org authored
into anubis.xiphis.org:/usr/home/antony/work/mysql-5.0-engines.merge
-
antony@pcg5ppc.xiphis.org authored
into anubis.xiphis.org:/usr/home/antony/work/mysql-5.1-engines.merge
-
antony@pcg5ppc.xiphis.org authored
into anubis.xiphis.org:/usr/home/antony/work/mysql-5.0-engines.merge
-
into anubis.xiphis.org:/usr/home/antony/work/mysql-4.1-engines.merge
-
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 9 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
-
antony@pcg5ppc.xiphis.org authored
into pcg5ppc.xiphis.org:/private/Network/Servers/anubis.xiphis.org/home/antony/work/p1-bug31473.1-merge-5.1-engines
-
antony@pcg5ppc.xiphis.org authored
"CSV does not work with NULL value in datetime fields" Attempting to insert a row with a NULL value for a DATETIME field results in a CSV file which the storage engine cannot read. Don't blindly assume that "0" is acceptable for all field types, Since CSV does not support NULL, we find out from the field the default non-null value. Do not permit the creation of a table with a nullable columns.
-
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.
-
istruewing@stella.local authored
The server crashed when a thread was killed while locking the general_log table at statement begin. The general_log table is handled like a performance schema table. The state of open tables is saved and cleared so that this table seems to be the only open one. Then this table is opened and locked. After writing, the table is closed and the open table state is restored. Before restoring, however, it is asserted that there is no current table open. After locking the table, mysql_lock_tables() checks if the thread was killed in between. If so, it unlocks the table and returns an error. open_ltable() just returns with the error and leaves closing of the table to close_thread_tables(), which is called at statement end. open_performance_schema_table() did not take this into account. It assumed that a failed open_ltable() would not leave an open table behind. Fixed by closing thread tables after open_ltable() and before restore_backup_open_tables_state() if the thread was killed. No test case. It requires correctly timed parallel execution. Since this bug was detected by the test suite, it seems dispensable to add another test.
-
- 17 Oct, 2007 14 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.
-
mattiasj@mattiasj-laptop.(none) authored
table to partitioned Problem: Crashed because usage of an uninitialised mutex when auto_incrementing a partitioned temporary table Fix: Only locking (using the mutex) if not temporary table.
-
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
-
- 16 Oct, 2007 3 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
-
thek@adventure.(none) authored
into adventure.(none):/home/thek/Development/cpp/mysql-5.1-runtime
-