- 29 Jul, 2006 1 commit
-
-
- 28 Jul, 2006 3 commits
-
-
the usable range to 0..1000 (0 disables the thread throttling).
-
-
-
- 26 Jul, 2006 5 commits
-
-
Changes in SQL parser: * Change default mode of SELECT from "lock in share mode" to "consistent read". * Remove support from SELECT for specifying "consistent read". * Add support in SELECT for specifying "lock in share mode". * Change all uses of SQL parser to specify "lock in share mode". * Modify syntax so that the only valid top-level statement is a procedure definition, since it's the only one that actually works. * Add support for lock waits.
-
aivanov@mysqld.localdomain authored
into mysql.com:/home/alexi/innodb/mysql-5.1-work Null merge.
-
aivanov@mysql.com authored
-
aivanov@mysql.com authored
into mysql.com:/home/alexi/innodb/mysql-5.0-work Null merge.
-
aivanov@mysql.com authored
-
- 12 Jul, 2006 3 commits
-
-
mkindahl@dl145k.mysql.com authored
into dl145k.mysql.com:/data0/mkindahl/bk/mysql-5.1-new-rpl
-
mkindahl@dl145k.mysql.com authored
into dl145k.mysql.com:/data0/mkindahl/bk/mysql-5.1-new-rpl
-
mkindahl@dl145k.mysql.com authored
-
- 11 Jul, 2006 5 commits
-
-
joerg@trift2. authored
into trift2.:/M51/merge-5.1
-
joerg@trift2. authored
into trift2.:/M51/merge-5.1
-
mkindahl@dl145k.mysql.com authored
into dl145k.mysql.com:/data0/mkindahl/bk/MERGE/mysql-5.1-merge
-
ingo/mydev@chilla.local authored
into chilla.local:/home/mydev/mysql-5.1-amerge
-
mkindahl@dl145k.mysql.com authored
into dl145k.mysql.com:/data0/mkindahl/bk/MERGE/mysql-5.0-merge
-
- 10 Jul, 2006 16 commits
-
-
cmiller@zippy.(none) authored
into zippy.(none):/home/cmiller/work/mysql/merge/mysql-5.1
-
patg@govinda.patg.net authored
-
aelkin/elkin@andrepl.(none) authored
into andrepl.(none):/home/elkin/MySQL/TEAM/FIXES/5.1/20919_temp_nlog
-
guilhem@gbichot3.local authored
We now reset the THD members related to auto_increment+binlog in MYSQL_LOG::write(). This is better than in THD::cleanup_after_query(), which was not able to distinguish between SELECT myfunc1(),myfunc2() and INSERT INTO t SELECT myfunc1(),myfunc2() from a binlogging point of view. Rows_log_event::exec_event() now calls lex_start() instead of mysql_init_query() because the latter now does too much (it resets the binlog format).
-
aelkin/elkin@andrepl.(none) authored
into andrepl.(none):/home/elkin/MySQL/TEAM/FIXES/5.1/20919_temp_nlog
-
guilhem@gbichot3.local authored
into gbichot3.local:/home/mysql_src/mysql-5.0
-
pekka@orca.ndb.mysql.com authored
-
pekka@orca.ndb.mysql.com authored
into orca.ndb.mysql.com:/space_old/pekka/ndb/version/my51-bug18781
-
pekka@orca.ndb.mysql.com authored
-
pekka@orca.ndb.mysql.com authored
into orca.ndb.mysql.com:/space_old/pekka/ndb/version/my51-bug18781
-
pekka@orca.ndb.mysql.com authored
-
guilhem@gbichot3.local authored
into gbichot3.local:/home/mysql_src/mysql-5.1
-
mats@romeo.(none) authored
into romeo.(none):/home/bk/b20821-mysql-5.1-new-rpl
-
ingo/mydev@chilla.local authored
into chilla.local:/home/mydev/mysql-5.1-aid
-
into dsl-hkigw8-feb1fb00-100.dhcp.inet.fi:/usr_rh9/home/elkin.rh9/MySQL/TEAM/FIXES/5.0/20919_temp_nlog
-
mats@romeo.(none) authored
set properly.
-
- 09 Jul, 2006 7 commits
-
-
closing temp tables through end_thread had a flaw in binlog-off branch of close_temporary_tables where next table to close was reset via table->next for (table= thd->temporary_tables; table; table= table->next) which was wrong since the current table instance got destoyed at close_temporary(table, 1); The fix adapts binlog-on branch method to engage the loop's internal 'next' variable which holds table->next prior table's destoying.
-
guilhem@gbichot3.local authored
into gbichot3.local:/home/mysql_src/mysql-5.1
-
guilhem@gbichot3.local authored
-
guilhem@gbichot3.local authored
into gbichot3.local:/home/mysql_src/mysql-5.1
-
guilhem@gbichot3.local authored
-
guilhem@gbichot3.local authored
-
guilhem@gbichot3.local authored
into gbichot3.local:/home/mysql_src/mysql-5.1
-