An error occurred fetching the project authors.
- 27 Aug, 2003 4 commits
-
-
jani@rhols221.adsl.netsonic.fi authored
into rhols221.adsl.netsonic.fi:/home/my/bk/mysql-4.0
-
miguel@hegel.local authored
-
jani@rhols221.adsl.netsonic.fi authored
and --defaults-file is a non-existing or non-regular file. Bug#755
-
lenz@mysql.com authored
-
- 26 Aug, 2003 7 commits
-
-
monty@narttu.mysql.fi authored
into narttu.mysql.fi:/my/mysql-4.0
-
monty@narttu.mysql.fi authored
Added TCP/IP read/write timeout for windows Check on windows if second server is started with same TCP/IP port
-
serg@serg.mylan authored
do not try to "analyze" or "sort index" in the table that has no indexes or no records if --check-only-changed option is used. It's because such a table is never marked as "analyzed" or "sorted", so --check-only-changed doesn't work
-
serg@serg.mylan authored
into serg.mylan:/usr/home/serg/Abk/mysql-4.0
-
serg@serg.mylan authored
fix ANALYZE TBALE to never generate rec_per_key_part < 1, as it prevent the table from being marked as analyzed (and the value is meaningless anyway)
-
Sinisa@sinisa.nasamreza.org authored
-
lenz@mysql.com authored
other operating systems - some implementations of "hostname" simply set the host name to "-f" instead of giving an error about an unkown option
-
- 25 Aug, 2003 7 commits
-
-
guilhem@mysql.com authored
into mysql.com:/home/mysql_src/mysql-4.0
-
monty@narttu.mysql.fi authored
into narttu.mysql.fi:/my/mysql-4.0
-
guilhem@mysql.com authored
Don't start the SQL slave thread with SQL_BIG_SELECTS; it's better to inhibate max_join_size instead.
-
monty@narttu.mysql.fi authored
Fixed deadlock bug when doing resize of key buffer while key buffer was in active use
-
guilhem@mysql.com authored
into mysql.com:/home/mysql_src/mysql-4.0
-
guilhem@mysql.com authored
For example the Binlog_dump thread (on the master) sometimes showed "Slave:". And there were confusing messages where "binlog" was employed instead of "relay log".
-
monty@narttu.mysql.fi authored
Fix unlock error in myisamchk on windows when doing --sort-index Use SetFilePointer instead of SetFilePointerEx
-
- 24 Aug, 2003 1 commit
-
-
heikki@hundin.mysql.fi authored
strerror() does not work in Windows
-
- 23 Aug, 2003 5 commits
-
-
guilhem@mysql.com authored
OPTION_BIG_SELECTS.
-
guilhem@mysql.com authored
into mysql.com:/home/mysql_src/mysql-4.0
-
guilhem@mysql.com authored
when the SQL thread stops, set rli->inside_transaction to 0. This is needed if the user later restarts replication from a completely different place where there are only autocommit statements. * Detect the case where the master died while flushing the binlog cache to the binlog and stop with error. Cannot add a testcase for this in 4.0 (I tested it manually) as the slave always runs with --skip-innodb.
-
monty@narttu.mysql.fi authored
into narttu.mysql.fi:/my/mysql-4.0
-
monty@narttu.mysql.fi authored
-
- 22 Aug, 2003 6 commits
-
-
Sinisa@sinisa.nasamreza.org authored
-
Sinisa@sinisa.nasamreza.org authored
Fix for a bug #878
-
guilhem@mysql.com authored
into mysql.com:/home/mysql_src/mysql-4.0
-
guilhem@mysql.com authored
fix for BUG#1113 "INSERT into non-trans table SELECT ; ROLLBACK" does not send warning" and fix for BUG#873 "In transaction, INSERT to non-trans table is written too early to binlog". Now we don't always write the non-trans update immediately to the binlog; if there is something in the binlog cache we write it to the binlog cache (because the non-trans update could depend on a trans table which was modified earlier in the transaction); then in case of ROLLBACK, we write the binlog cache to the binlog, wrapped with BEGIN/ROLLBACK. This guarantees that the slave does the same updates. For ROLLBACK TO SAVEPOINT: when we execute a SAVEPOINT command we write it to the binlog cache. At ROLLBACK TO SAVEPOINT, if some non-trans table was updated, we write ROLLBACK TO SAVEPOINT to the binlog cache; when the transaction terminates (COMMIT/ROLLBACK), the binlog cache will be flushed to the binlog (because of the non-trans update) so we'll have SAVEPOINT and ROLLBACK TO SAVEPOINT in the binlog. Apart from this rare case of updates of mixed table types in transaction, the usual way is still clear the binlog cache at ROLLBACK, or chop it at ROLLBACK TO SAVEPOINT (meaning the SAVEPOINT command is also chopped, which is fine). Note that BUG#873 encompasses subbugs 1) and 2) of BUG#333 "3 binlogging bugs when doing INSERT with mixed InnoDB/MyISAM".
-
monty@narttu.mysql.fi authored
into narttu.mysql.fi:/my/mysql-4.0
-
monty@narttu.mysql.fi authored
Move test that uses many tables (in query_cache.test) to separate test so that we can get it 'skipped' instead of 'failed' on system where we can't open many files.
-
- 21 Aug, 2003 10 commits
-
-
serg@serg.mylan authored
-
serg@serg.mylan authored
-
serg@serg.mylan authored
into serg.mylan:/usr/home/serg/Abk/mysql
-
serg@serg.mylan authored
-
serg@serg.mylan authored
into serg.mylan:/usr/home/serg/Abk/mysql-4.0
-
serg@serg.mylan authored
-
lenz@mysql.com authored
the embedded server (it was missing in the previous push)
-
serg@serg.mylan authored
into serg.mylan:/usr/home/serg/Abk/mysql-4.0
-
serg@serg.mylan authored
-
guilhem@mysql.com authored
Let's say the lack of comments did not help me ;) Copying it back again and adding comments; now 3.23->4.0 replication of LOAD DATA INFILE works again.
-