- 14 Jul, 2003 2 commits
-
-
ram@mysql.r18.ru authored
-
ram@mysql.r18.ru authored
into mysql.r18.ru:/usr/home/ram/work/4.0
-
- 13 Jul, 2003 2 commits
-
-
heikki@hundin.mysql.fi authored
Put back a 50 millisecond sleep in too high concurrency situations which I removed in the previous push; count also such sleeping threads to the InnoDB queue in SHOW INNODB STATUS
-
heikki@hundin.mysql.fi authored
Fix a benign bug introduced in 4.0.14: InnoDB could complain 'Error: trying to declare trx to enter InnoDB' if several threads tried to init the auto-inc counter for the same table at the same time; in theory, the bug could even lead to a hang of the server, but that shuld be extremely improbable
-
- 12 Jul, 2003 6 commits
-
-
heikki@hundin.mysql.fi authored
Allow also O_DIRECT as innodb_flush_method; it only affects writing to data files
-
paul@ice.local authored
fix typo.
-
guilhem@mysql.com authored
-
guilhem@mysql.com authored
-
guilhem@mysql.com authored
into mysql.com:/home/mysql_src/mysql-4.0
-
guilhem@mysql.com authored
-
- 11 Jul, 2003 6 commits
-
-
lenz@mysql.com authored
port number can be different from 3306 when doing the release builds with Do-compile, therefore it has to be replaced with the correct value during the test run using the "--replace_result" function.
-
lenz@mysql.com authored
-
lenz@mysql.com authored
ChangeSet was not sufficient to get the full ChangeLog between two released versions (when using "--changelog=last") as merging between trees also merges the BK tags. Now we explicitely search for the last tagged ChangeSet that matches our major+minor version number, which should match the last ChangeSet used for the previous release.
-
guilhem@mysql.com authored
a safer way of initing the mutexes in MYSQL_LOG. is_open() is now always thread-safe. See each file for details.
-
ram@mysql.r18.ru authored
-
ram@mysql.r18.ru authored
into mysql.r18.ru:/usr/home/ram/work/4.0
-
- 10 Jul, 2003 2 commits
-
-
guilhem@mysql.com authored
"mysqlhotcopy fails to copy tables but does not indicate a failure" ("does not indicate a failure"); this is about "mysqlhotcopy fails to copy tables".
-
ram@mysql.r18.ru authored
Now INTERVAL(NULL, N1, N2, ...) returns NULL.
-
- 09 Jul, 2003 2 commits
-
-
lenz@mysql.com authored
into mysql.com:/space/my/mysql-4.0-build
-
lenz@mysql.com authored
override CC/CXX when using a special compiler) - the RPM should now build on AMD64 and IA64, too
-
- 08 Jul, 2003 14 commits
-
-
monty@mashka.mysql.fi authored
into mashka.mysql.fi:/home/my/mysql-4.0
-
monty@mashka.mysql.fi authored
-
lenz@mysql.com authored
into mysql.com:/space/my/mysql-4.0
-
lenz@mysql.com authored
(BUG#812)
-
monty@mashka.mysql.fi authored
into mashka.mysql.fi:/home/my/mysql-4.0
-
monty@mashka.mysql.fi authored
Removed double my_thread_end() which caused fatal error on windows if mysqld died on startup
-
heikki@hundin.mysql.fi authored
Prevent the user from creating InnoDB tables with > 1000 columns
-
paul@teton.kitebird.com authored
No commit message
-
paul@teton.kitebird.com authored
Undo serg's patch that used my_print_defaults, and instead simply do not define $opt{user}. This allows the script to use option files properly.
-
serg@serg.mylan authored
into serg.mylan:/usr/home/serg/Abk/mysql-4.0
-
serg@serg.mylan authored
-
guilhem@mysql.com authored
into mysql.com:/home/mysql_src/mysql-4.0
-
guilhem@mysql.com authored
BUG#797 "If query ignored on slave (replicate-ignore-table) the slave still checks if the returned error (0) is the same as the one on the master, whereas it shouldn't test this. Plus a new test for BUG#797.
-
heikki@hundin.mysql.fi authored
A cosmetic change: set trx id to zero at creation so that SHOW INNODB STATUS does not print a random value for the id of a transaction object for which the transaction has never been started yet (for example, running SHOW INNODB STATUS as the first command from a mysql prompt printed a random id for the trx object associated with the session itself running the SHOW INNODB STATUS command)
-
- 07 Jul, 2003 5 commits
-
-
serg@serg.mylan authored
-
serg@serg.mylan authored
into serg.mylan:/usr/home/serg/Abk/mysql-4.0
-
serg@serg.mylan authored
-
serg@serg.mylan authored
still no rec. descent
-
heikki@hundin.mysql.fi authored
Fix bug: if a DELETE failed in a FOREIGN KEY error and it had already deleted some rows, then MySQL did not roll back the failed SQL statement, and also wrote it to the binlog
-
- 06 Jul, 2003 1 commit
-
-
guilhem@mysql.com authored
into mysql.com:/home/mysql_src/mysql-4.0
-