- 12 Sep, 2006 4 commits
-
-
andrey@example.com authored
-
andrey@example.com authored
-
andrey@example.com authored
-
andrey@example.com authored
Remove SHOW SCHEDULER STATUS command and migrate the information output to `mysqladmin debug` (COM_DEBUG) SHOW SCHEDULER STATUS was introduced in 5.1.11, provided some debug information about event scheduler internals and was enabled only in debug builds.
-
- 07 Sep, 2006 1 commit
-
-
andrey@example.com authored
-
- 06 Sep, 2006 1 commit
-
-
ahristov@bk-internal.mysql.com authored
into bk-internal.mysql.com:/data0/bk/mysql-5.1-wl3337
-
- 01 Sep, 2006 8 commits
-
-
anozdrin/alik@alik. authored
into alik.:/mnt/raid/alik/MySQL/devel/5.1-rt-merged
-
andrey@example.com authored
-
andrey@example.com authored
-
andrey@example.com authored
-
andrey@example.com authored
into example.com:/work/mysql-5.1-runtime-wl3337
-
andrey@example.com authored
This is a post-review patch. Fixes the typelib implementation, available only in 5.1.11. --event-scheduler cmdline : DISABLED | ON | OFF | 0 | 1 DISABLED - makes the scheduler unavailable during the server run (ON|1)- When the server is started the scheduler will be started. It can be stopped and restarted by setting appropriate values to GLOBAL event_scheduler (OFF|0)- When the server is started, the scheduler won't be started. It can be started and again stopped by setting appropriate values to GLOBAL event_scheduler. _DEFAULT_ value The GLOBAL variable event_scheduler can have the following values: OFF | ON | 0 | 1 DISABLED is not possible and every attempt will end with an error that it's not a valid value for the variable. OFF | 0 - This is the pre-5.1.11 behavior - The scheduler stops, if not already stopped, and can be started again by setting the value of the variable to ON|1. ON | 1 - This is the pre-5.1.11 behavior - The scheduler starts, if not already started, and can be stopped again by setting the value of the variable to OFF|0.
-
evgen@moonbone.local authored
into moonbone.local:/work/tmp_merge-5.1-mysql
-
mikael/pappa@dator5.(none) authored
-
- 31 Aug, 2006 17 commits
-
-
mikael/pappa@dator5.(none) authored
into dator5.(none):/home/pappa/push_clone
-
mikael/pappa@dator5.(none) authored
into dator5.(none):/home/pappa/push_clone
-
andrey@fifo.vaih.whnetz authored
into fifo.vaih.whnetz:/work/mysql-5.1-wl3337-tree2
-
andrey@fifo.vaih.whnetz authored
This patch makes the relationship between Event_scheduler and Event_queue unidirectional from the former to the latter. The change is that the conditional on which the scheduler sleeped has been moved to the Event_queue and the latter does not call anymore Event_scheduler::queue_changed(), which in turn has be removed.
-
anozdrin/alik@alik. authored
The problem was in dummy grep on AIX and HPUX. The fix is to use more portable patterns. The patch is only for test suite (i.e. does not touch server codebase).
-
rburnett@bk-internal.mysql.com authored
into bk-internal.mysql.com:/data0/bk/mysql-5.1-kt
-
mikael/pappa@dator5.(none) authored
-
jonas@perch.ndb.mysql.com authored
into perch.ndb.mysql.com:/home/jonas/src/mysql-5.1
-
mikael/pappa@dator5.(none) authored
into dator5.(none):/home/pappa/push_clone
-
mikael/pappa@dator5.(none) authored
into dator5.(none):/home/pappa/push_clone
-
gluh@mysql.com/gluh.(none) authored
fixed error message
-
kostja@bodhi.local authored
into bodhi.local:/opt/local/work/mysql-5.1-runtime-merge
-
jonas@perch.ndb.mysql.com authored
into perch.ndb.mysql.com:/home/jonas/src/mysql-5.1
-
mikael/pappa@dator5.(none) authored
into dator5.(none):/home/pappa/bug21388
-
mikael/pappa@dator5.(none) authored
into dator5.(none):/home/pappa/bug21388
-
mikael/pappa@dator5.(none) authored
Review fixes
-
evgen@moonbone.local authored
into moonbone.local:/work/tmp_merge-5.1-opt-mysql
-
- 30 Aug, 2006 6 commits
-
-
kostja@bodhi.local authored
-
rburnett@bk-internal.mysql.com authored
into bk-internal.mysql.com:/data0/bk/mysql-5.1-kt
-
evgen@moonbone.local authored
After merge changes
-
Reggie@blackhole. authored
-
georg@lmy002.wdf.sap.corp authored
CMake versions > 2.4 allow linking to STATIC or SHARED libraries only.
-
gluh@mysql.com/gluh.(none) authored
skip engine handling if engine is disabled
-
- 29 Aug, 2006 3 commits
-
-
kostja@bodhi.local authored
into bodhi.local:/opt/local/work/mysql-5.1-runtime-merge
-
jonas@perch.ndb.mysql.com authored
into perch.ndb.mysql.com:/home/jonas/src/mysql-5.1-new-ndb
-
kostja@bodhi.local authored
doesn't find the column" When a user was using 4.1 tables with VARCHAR column and 5.0 server and a query that used a temporary table to resolve itself, the table metadata for the varchar column sent to client was incorrect: MYSQL_FIELD::table member was empty. The bug was caused by implicit "upgrade" from old VARCHAR to new VARCHAR hard-coded in Field::new_field, which did not preserve the information about the original table. Thus, the field metadata of the "upgraded" field pointed to an auxiliary temporary table created for query execution. The fix is to copy the pointer to the original table to the new field.
-