- 01 Nov, 2007 2 commits
-
-
kostja@bodhi.(none) authored
-
kostja@bodhi.(none) authored
into bodhi.(none):/opt/local/work/mysql-5.1-runtime-inc-2
-
- 31 Oct, 2007 18 commits
-
-
kostja@bodhi.(none) authored
-
kostja@bodhi.(none) authored
during udf initialization. The bug is spotted while working on Bug 12713. If a user-defined function was used in a SELECT statement, and an error would occur during UDF initialization, this error would not terminate execution of the SELECT, but rather would be converted to a warning. The fix is to use a stack buffer to store the message from udf_init instead of private my_error() buffer.
-
kostja@bodhi.(none) authored
check_user()/check_connection()/check_for_max_user_connections(). This is a pre-requisite patch for the fix for Bug#12713 "Error in a stored function called from a SELECT doesn't cause ROLLBACK of statem" Implement review comments.
-
kostja@bodhi.(none) authored
into bodhi.(none):/opt/local/work/mysql-5.1-runtime-inc
-
kostja@bodhi.(none) authored
-
davi@endora. authored
into endora.local:/Users/davi/mysql/mysql-5.1-runtime
-
davi@endora.local/endora authored
-
kostja@bodhi.(none) authored
Add select_send::cleanup. Fix a compilation warning. Issues spotted while working on the fix for Bug#12713.
-
kostja@bodhi.(none) authored
into bodhi.(none):/opt/local/work/mysql-5.1-runtime-inc
-
kostja@bodhi.(none) authored
No functionality added or changed. This is a pre-requisite for the fix for Bug#12713 Error in a stored function called from a SELECT doesn't cause ROLLBACK of statem Address post-review comments.
-
anozdrin/alik@station. authored
into station.:/mnt/raid/alik/MySQL/devel/5.1-rt-bug31649
-
thek@adventure.(none) authored
into adventure.(none):/home/thek/Development/cpp/mysql-5.1-runtime
-
thek@adventure.(none) authored
into adventure.(none):/home/thek/Development/cpp/bug31347/my51-bug31347
-
thek@adventure.(none) authored
Dropping users causes huge increase in memory usage because field values were allocated on the server memory root for temporary usage but never deallocated. This patch changes the target memory root to be that of the thread handler instead since this root is cleared between each statement.
-
anozdrin/alik@station. authored
SHOW PROCESSLIST. The problem was a race condition: if the Event Scheduler was not quick enough, the following scenario happens: - The Event Scheduler picks up the created event; - The event is executed; - event_scheduler_thread->proc_info is set to NULL; - The client issues SELECT FROM I_S. The fix is to wait for the Event Scheduler to reach 'Waiting for next activation' state.
-
anozdrin/alik@station. authored
-
davi@endora.local authored
into endora.local:/Users/davi/mysql/mysql-5.1-runtime
-
davi@endora.local authored
into endora.local:/Users/davi/mysql/bugs/31669-5.1
-
- 30 Oct, 2007 8 commits
-
-
davi@endora.local authored
into endora.local:/Users/davi/mysql/mysql-5.1-runtime
-
davi@endora.local authored
The SET PASSWORD statement is non-transactional (no explicit transaction boundaries) in nature and hence is forbidden inside stored functions and triggers, but it weren't being effectively forbidden. The implemented fix is to issue a implicit commit with every SET PASSWORD statement, effectively prohibiting these statements in stored functions and triggers.
-
kostja@bodhi.(none) authored
and convert it to a warning instead of direct manipulation with the thread error stack. Fix a bug in handler::print_erorr when a garbled message was printed for HA_ERR_NO_SUCH_TABLE. This is a pre-requisite patch for the fix for Bug#12713 Error in a stored function called from a SELECT doesn't cause ROLLBACK of statem
-
kostja@bodhi.(none) authored
into bodhi.(none):/opt/local/work/mysql-5.1-runtime-inc-2
-
kostja@bodhi.(none) authored
in THD. In future the error may be stored elsewhere (not in net.report_error) and it's important to start using an opaque getter to simplify merges.
-
davi@moksha.com.br authored
into moksha.local:/Users/davi/mysql/mysql-5.0-runtime
-
kostja@bodhi.(none) authored
-
kostja@bodhi.(none) authored
This is important for a development environment where not all source files are checked out.
-
- 29 Oct, 2007 5 commits
-
-
malff@lambda.weblab authored
into lambda.weblab:/home/malff/TREE/mysql-5.1-rt-merge
-
malff@lambda.weblab authored
into lambda.weblab:/home/malff/TREE/mysql-5.1-rt-merge
-
malff@lambda.weblab authored
into lambda.weblab:/home/malff/TREE/mysql-5.0-rt-merge
-
anozdrin/alik@station. authored
rebuild the table. The problem was that ROW_FORMAT clause in ALTER TABLE did not trigger table reconstruction. The fix is to rebuild a table if ROW_FORMAT is specified.
-
gluh@eagle.(none) authored
into mysql.com:/home/gluh/MySQL/Merge/5.1-opt
-
- 25 Oct, 2007 2 commits
-
-
joerg@trift2. authored
to get rid of a name clash among *deleted* files on case-insignificant file systems.
-
malff@lambda.hsd1.co.comcast.net. authored
The root cause of this defect is that a call to my_error() is using a 'LEX_STRING' parameter instead of a 'char*' This patch fixes the failing calls to my_error(), as well as similar calls found during investigation. This is a compiling bug (see the instrumentation in the bug report), no test cases provided.
-
- 24 Oct, 2007 2 commits
-
-
gluh@mysql.com/eagle.(none) authored
-
anozdrin/alik@station. authored
into station.:/mnt/raid/alik/MySQL/devel/5.1-rt
-
- 23 Oct, 2007 3 commits
-
-
gluh@mysql.com/eagle.(none) authored
-
gluh@eagle.(none) authored
into mysql.com:/home/gluh/MySQL/Merge/5.1-opt
-
gluh@eagle.(none) authored
into mysql.com:/home/gluh/MySQL/Merge/5.0-opt
-