- 16 Oct, 2007 5 commits
-
-
thek@adventure.(none) authored
into adventure.(none):/home/thek/Development/cpp/mysql-5.1-runtime
-
thek@adventure.(none) authored
test programs.
-
kostja@bodhi.(none) authored
(this is a backward-compatible change).
-
thek@adventure.(none) authored
into adventure.(none):/home/thek/Development/cpp/mysql-5.1-runtime
-
thek@adventure.(none) authored
The embedded version of the server doesn't use column level grants, and the compile directive NO_EMBEDDED_ACCESS_CHECKS should be checked instead of the redundant HAVE_QUERY_CACHE (which is always the case) to determine if column level grants should be compiled or not.
-
- 15 Oct, 2007 5 commits
-
-
dkatz@damien-katzs-computer.local authored
-
dkatz@damien-katzs-computer.local authored
into damien-katzs-computer.local:/Users/dkatz/mysql-5.1-runtime
-
kostja@bodhi.(none) authored
explicitly.
-
kostja@bodhi.(none) authored
-
kostja@bodhi.(none) authored
of the stored procedure cursors (materialized on disk).
-
- 12 Oct, 2007 3 commits
-
-
davi@moksha.com.br authored
into moksha.com.br:/Users/davi/mysql/mysql-5.1-runtime
-
davi@moksha.com.br authored
into moksha.com.br:/Users/davi/mysql/mysql-5.1-runtime
-
davi@moksha.com.br authored
If mysql_lock_tables fails because the lock was aborted, we need to reset thd->some_tables_delete, otherwise we might loop indefinitely because handler's tables are not closed in a standard way, meaning that close_thread_tables() (which resets some_tables_deleted) is not used. This patch fixes sporadical failures of handler_myisam/innodb tests which were introduced by previous fix for this bug.
-
- 11 Oct, 2007 7 commits
-
-
malff/marcsql@weblab.(none) authored
into weblab.(none):/home/marcsql/TREE/mysql-5.1-27858-b
-
malff/marcsql@weblab.(none) authored
Before this patch, failures to write to the log tables (mysql.slow_log and mysql.general_log) were improperly printed (the time was printed twice), or not printed at all. With this patch, failures to write to the log tables is reported in the error log, for all cases of failures.
-
davi@moksha.com.br authored
"DECLARE CURSOR FOR SHOW ..." is a syntax that currently appears to work, but is untested for some SHOW commands and does not work for other SHOW commands. Since this is an un-intended feature that leaked as a result of a coding bug (in the parser grammar), the correct fix is to fix the grammar to not accept this construct. In other words, "DECLARE CURSOR FOR SHOW <other commands that don't work>" is not considered a bug, and we will not implement other features to make all the SHOW commands usable inside a cursor just because someone exploited a bug.
-
anozdrin/alik@station. authored
mysql_change_user(). The problem was that THD::ull was not reset in THD::cleanup(). The fix is to reset it.
-
davi@moksha.com.br authored
-
davi@moksha.com.br authored
into moksha.com.br:/Users/davi/mysql/bugs/31409-5.1
-
davi@moksha.com.br authored
static but it's still used by another compilation unit. Remove static qualifier from do_command definition.
-
- 10 Oct, 2007 12 commits
-
-
davi@moksha.com.br authored
into moksha.com.br:/Users/davi/mysql/mysql-5.1-runtime
-
davi@moksha.com.br authored
into moksha.com.br:/Users/davi/mysql/mysql-5.1-runtime
-
davi@moksha.com.br authored
into moksha.com.br:/Users/davi/mysql/mysql-5.1-runtime
-
davi@moksha.com.br authored
into moksha.com.br:/Users/davi/mysql/mysql-5.1-runtime
-
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/bugs/21587-5.1
-
dkatz@damien-katzs-computer.local authored
into damien-katzs-computer.local:/Users/dkatz/mysql-5.1-runtime
-
anozdrin/alik@station. authored
of SQL_BIG_SELECTS. The bug was that SQL_BIG_SELECTS was not properly set in COM_CHANGE_USER. The fix is to update SQL_BIG_SELECTS properly.
-
anozdrin/alik@station. authored
-
anozdrin/alik@station. authored
into station.:/mnt/raid/alik/MySQL/devel/5.1-rt-merged
-
malff@lambda.hsd1.co.comcast.net. authored
-
- 09 Oct, 2007 5 commits
-
-
davi@moksha.com.br authored
into moksha.com.br:/Users/davi/mysql/push/bugs/31409-5.0
-
davi@moksha.local authored
This deadlock occurs when a client issues a HANDLER ... OPEN statement that tries to open a table that has a pending name-lock on it by another client that also needs a name-lock on some other table which is already open and associated to a HANDLER instance owned by the first client. The deadlock happens because the open_table() function will back-off and wait until the name-lock goes away, causing a circular wait if some other name-lock is also pending for one of the open HANDLER tables. Such situation, for example, can be easily repeated by issuing a RENAME TABLE command in such a way that the existing table is already open as a HANDLER table by another client and this client tries to open a HANDLER to the new table name. The solution is to allow handler tables with older versions (marked for flush) to be closed before waiting for the name-lock completion. This is safe because no other name-lock can be issued between the flush and the check for pending name-locks. The test case for this bug is going to be committed into 5.1 because it requires a test feature only avaiable in 5.1 (wait_condition).
-
davi@moksha.local authored
into moksha.local:/Users/davi/mysql/push/mysql-5.1-runtime
-
anozdrin/alik@station. authored
-
anozdrin/alik@station. authored
into station.:/mnt/raid/alik/MySQL/devel/5.1-rt-merged
-
- 08 Oct, 2007 3 commits
-
-
malff@lambda.hsd1.co.comcast.net. authored
-
dkatz@damien-katzs-computer.local authored
into damien-katzs-computer.local:/Users/dkatz/mysql-5.1-runtime
-
anozdrin/alik@station. authored
-