- 09 Apr, 2007 1 commit
-
-
iggy@alf. authored
into alf.:D:/src/mysql-5.1-maint_pt
-
- 06 Apr, 2007 5 commits
-
-
kostja@vajra.(none) authored
into vajra.(none):/opt/local/work/mysql-5.1-runtime
-
anozdrin/alik@ibm. authored
-
kostja@vajra.(none) authored
This will hopefully fix events.test failure on vmware-win32, where scheduling is very primitive.
-
anozdrin/alik@ibm. authored
-
kostja@vajra.(none) authored
into vajra.(none):/opt/local/work/mysql-5.1-runtime
-
- 05 Apr, 2007 12 commits
-
-
kostja@vajra.(none) authored
-
kostja@vajra.(none) authored
-
kostja@vajra.(none) authored
Apparently it's the only platform in pushbuild where we compile without openssl.
-
kostja@vajra.(none) authored
-
kostja@vajra.(none) authored
-
kostja@vajra.(none) authored
-
kostja@vajra.(none) authored
into vajra.(none):/opt/local/work/mysql-5.1-c1
-
kostja@vajra.(none) authored
Bug#23631 "Events: SHOW VARIABLES doesn't work when mysql.event is damaged:
-
tsmith@siva.hindu.god authored
into siva.hindu.god:/home/tsmith/m/bk/maint/51
-
kostja@vajra.(none) authored
into vajra.(none):/opt/local/work/mysql-5.1-c1
-
kostja@vajra.(none) authored
when there are no up-to-date system tables to support it: - initialize the scheduler before reporting "Ready for connections". This ensures that warnings, if any, are printed before "Ready for connections", and this message is not mangled. - do not abort the scheduler if there are no system tables - check the tables once at start up, remember the status and disable the scheduler if the tables are not up to date. If one attempts to use the scheduler with bad tables, issue an error message. - clean up the behaviour of the module under LOCK TABLES and pre-locking mode - make sure implicit commit of Events DDL works as expected. - add more tests Collateral clean ups in the events code. This patch fixes Bug#23631 Events: SHOW VARIABLES doesn't work when mysql.event is damaged
-
msvensson@pilot.blaudden authored
-
- 04 Apr, 2007 7 commits
-
-
kostja@vajra.(none) authored
-
tsmith@quadxeon.mysql.com authored
into quadxeon.mysql.com:/benchmarks/ext3/TOSAVE/tsmith/bk/maint/mrg04/51
-
tsmith@quadxeon.mysql.com authored
When MySQL logged slow query information to a CSV table, it stored the query_time and lock_time values with an incorrect formula. If the time was over 59 seconds, this caused incorrect statistics (either the slow query was not logged, or the time was far from correct). This change fixes the method used to store those TIME values in the slow_log table.
-
tsmith@quadxeon.mysql.com authored
-
tsmith@quadxeon.mysql.com authored
into quadxeon.mysql.com:/benchmarks/ext3/TOSAVE/tsmith/bk/maint/mrg04/51
-
tsmith@quadxeon.mysql.com authored
into quadxeon.mysql.com:/benchmarks/ext3/TOSAVE/tsmith/bk/maint/mrg04/50
-
tsmith@quadxeon.mysql.com authored
into quadxeon.mysql.com:/benchmarks/ext3/TOSAVE/tsmith/bk/maint/mrg04/51
-
- 03 Apr, 2007 9 commits
-
-
Reggie@vm-xp. authored
This changeset fixes the problem where mysql, when run as a service, can't "detect" it's own data directory.
-
kostja@bodhi.local authored
-
msvensson@pilot.blaudden authored
-
msvensson@pilot.blaudden authored
-
kostja@bodhi.local authored
into bodhi.local:/opt/local/work/mysql-5.1-runtime
-
kostja@bodhi.local authored
into bodhi.local:/opt/local/work/mysql-5.1-runtime
-
msvensson@pilot.blaudden authored
-
msvensson@pilot.blaudden authored
into pilot.blaudden:/home/msvensson/mysql/mysql-5.1-maint
-
msvensson@pilot.blaudden authored
-
- 02 Apr, 2007 6 commits
-
-
iggy@recycle.(none) authored
into recycle.(none):/src/bug23491_ii/my50-bug23491_ii
-
iggy@recycle.(none) authored
into recycle.(none):/src/bug23491_ii/my51-bug23491_ii
-
iggy@recycle.(none) authored
-
kostja@bodhi.local authored
into bodhi.local:/opt/local/work/mysql-5.0-runtime
-
Kristofer.Pettersson@naruto. authored
-
msvensson@pilot.blaudden authored
-