- 03 Mar, 2005 5 commits
-
-
ramil@mysql.com authored
-
ramil@mysql.com authored
-
mysqldev@mysql.com authored
into mysql.com:/data0/mysqldev/my/mysql-5.0-merge
-
mysqldev@mysql.com authored
committing this deletion of federated.disabled, which was already committed in another tree apparently; just to make bk happy.
-
patg@krsna.patg.net authored
-
- 02 Mar, 2005 24 commits
-
-
petr@mysql.com authored
into mysql.com:/home/cps/mysql/devel/im-fix-review
-
petr@mysql.com authored
-
patg@krsna.patg.net authored
into krsna.patg.net:/home/patg/mysql-5.0
-
guilhem@mysql.com authored
Last part of fix for BUG#7998 "Replication should be more clever about when to replicate RELEASE_LOCK()" + fixes after merge
-
ramil@mysql.com authored
into mysql.com:/usr/home/ram/work/4.1
-
patg@krsna.patg.net authored
into krsna.patg.net:/home/patg/mysql-5.0
-
ramil@mysql.com authored
-
guilhem@mysql.com authored
into mysql.com:/home/mysql_src/mysql-5.0-xa
-
guilhem@mysql.com authored
First part of fix for BUG#7998 "Replication should be more clever about when to replicate RELEASE_LOCK()" (next part is updating test results)
-
joerg@mysql.com authored
into mysql.com:/M50/mysql-5.0
-
serg@serg.mylan authored
into serg.mylan:/usr/home/serg/Abk/mysql-5.0
-
serg@serg.mylan authored
-
guilhem@mysql.com authored
-
marko@hundin.mysql.fi authored
-
ingo@mysql.com authored
After merge fix. The bugfix results in a different error message in this situation.
-
joerg@mysql.com authored
use function-wide declaration also for loop body.
-
guilhem@mysql.com authored
into mysql.com:/home/mysql_src/mysql-4.1-clean
-
guilhem@mysql.com authored
in slave SQL thread: if a transaction fails because of InnoDB deadlock or innodb_lock_wait_timeout exceeded, optionally retry the transaction a certain number of times (new variable --slave_transaction_retries).
-
ingo@mysql.com authored
-
serg@serg.mylan authored
into serg.mylan:/usr/home/serg/Abk/mysql-5.0
-
serg@serg.mylan authored
deadlock in MYSQL_LOG::new_file() style fixes
-
ingo@mysql.com authored
Added a check, if the table, which we are going to create, is open. This can happen if a MERGE mapped table is TRUNCATEd.
-
patg@krsna.patg.net authored
into krsna.patg.net:/home/patg/mysql-5.0
-
jan@hundin.mysql.fi authored
into hundin.mysql.fi:/home/jan/mysql-5.0
-
- 01 Mar, 2005 11 commits
-
-
heikki@hundin.mysql.fi authored
Correct indentation + some small style corrections
-
tomas@poseidon.ndb.mysql.com authored
updated ndb test makefile to make src dist complete
-
jani@ua141d10.elisa.omakaista.fi authored
into ua141d10.elisa.omakaista.fi:/home/my/bk/mysql-5.0
-
jani@ua141d10.elisa.omakaista.fi authored
-
marko@hundin.mysql.fi authored
delete_all_rows(): Revert previous change. The transaction has been marked started already in external_lock().
-
marko@hundin.mysql.fi authored
row_sel_store_mysql_rec(): Do not try to space-pad BLOB fields. (Bug #8771)
-
heikki@hundin.mysql.fi authored
into hundin.mysql.fi:/home/heikki/mysql-5.0
-
heikki@hundin.mysql.fi authored
In TRUNCATE TABLE, MySQL may call innobase_xa_prepare() even though there is no active transaction because it was committed in ha_innobase::delete_all_rows(); in innobase_xa_prepare() InnoDB starts then a new transaction; let us adjust the trx->active_trans flag accordingly
-
marko@hundin.mysql.fi authored
-
marko@hundin.mysql.fi authored
into hundin.mysql.fi:/home/marko/mysql-5.0
-
marko@hundin.mysql.fi authored
CREATE INDEX and DROP INDEX every 10,000 rows, similar to ALTER TABLE.
-