- 19 Jul, 2003 1 commit
-
-
unknown authored
-
- 01 Jul, 2003 2 commits
- 29 Jun, 2003 1 commit
-
-
unknown authored
was used with NULL value on NOT NULL column. (Bug #479) mysql-test/r/order_by.result: Update of results mysql-test/t/order_by.test: Test of new code sql/sql_select.cc: Fixed problem with lookup on NULL
-
- 26 Jun, 2003 2 commits
-
-
unknown authored
into eagle.mysql.r18.ru:/home/vva/work/BUG_479_/mysql-3.23 BitKeeper/etc/logging_ok: auto-union
-
unknown authored
mysql-test/r/user_var.result: added tests for user variables comparing (bug #551) mysql-test/t/user_var.test: added tests for user variables comparing (bug #551) BitKeeper/etc/logging_ok: Logging to logging@openlogging.org accepted
-
- 21 Jun, 2003 1 commit
-
-
unknown authored
repository (incredible that I forgot to push, but why not). So unfortunately the bugfix missed 3.23.57 and will be in .58 :( Instead of looking like working (bug #198), replication between a 3.23 slave and 4.0 master should frankly stop. Here we detect 4.0 masters in the 3.23 slave code when we see a strange Rotate event, and in that case we print an error and stop. 4.0.13 and older masters will be "often" caught (see the patch); 4.0.14 and newer masters will always be immediately caught. sql/slave.cc: Instead of looking like working (bug #198), replication between a 3.23 slave and 4.0 master should frankly stop. Here we detect 4.0 masters in the 3.23 slave code when we see a strange Rotate event, and in that case we print an error and stop. 4.0.13 and older masters will be "often" caught (see the patch); 4.0.14 and newer masters will always be immediately caught.
-
- 19 Jun, 2003 2 commits
- 18 Jun, 2003 3 commits
-
-
unknown authored
BitKeeper/etc/logging_ok: Logging to logging@openlogging.org accepted
-
unknown authored
into hundin.mysql.fi:/home/heikki/mysql
-
unknown authored
Backport the clust rec bug fix from 4.0 innobase/row/row0sel.c: Backport the clust rec bug fix from 4.0 innobase/row/row0vers.c: Backport the clust rec bug fix from 4.0
-
- 16 Jun, 2003 2 commits
-
-
unknown authored
into mysql.com:/home/mysql_src/mysql-3.23
-
unknown authored
as the already-stored timestamp. Now 'created' is used only to know if this is a first binlog or not. And we may re-use the superfluous bytes in 5.0 when we need room. sql/log_event.cc: This sort of reverts a change I made in 3.23.57. In 3.23.57 I set 'created' to 0 if this was a non-first binlog, so I made mysqlbinlog not print the "created xx" part if created == 0. While this was sensible, as 'created' is 0 or equal to the timestamp which is already stored in the event, we can always print "created xx" by using the timestamp, and leaving the use of 'created' only to know if this is a first binlog or not (which we print as "created at startup"). sql/log_event.h: In Start_log_event, 'created' is always the same as 'when', or O. We didn't need 4 bytes for this, a bit would have been enough (O or "same as 'when'"). Possibly in 5.0 we will re-use the useless bytes.
-
- 11 Jun, 2003 1 commit
-
-
unknown authored
Prevent on Windows starting of two mysqld instances on SAME InnoDB files: that could cause severe database corruption innobase/os/os0file.c: Prevent on Windows starting of two mysqld instances on SAME InnoDB files: that could cause severe database corruption
-
- 08 Jun, 2003 1 commit
-
-
unknown authored
BitKeeper/etc/logging_ok: Logging to logging@openlogging.org accepted
-
- 07 Jun, 2003 1 commit
-
-
unknown authored
Fix a bug: a race condition could cause that the first B-tree page splits would get a corrupt page directory, whic often results in the assertion in page_dir_find_slot(); found with a test of 3000 startups/shutdowns; it is not clear that this would have caused any corruption which users have reported innobase/page/page0page.c: Fix a bug: a race condition could cause that the first B-tree page splits would get a corrupt page directory, whic often results in the assertion in page_dir_find_slot(); found with a test of 3000 startups/shutdowns; it is not clear that this would have caused any corruption which users have reported
-
- 06 Jun, 2003 2 commits
-
-
unknown authored
Otherwise, we'll get questions from users about this curious 1970.
-
unknown authored
Fix for bug 254 : the first Start_log_event after server startup will have created=now(), whereas the next ones (FLUSH LOGS, auto rotation) will have created=0. Before this, it was always now(). This way, slaves >=4.0.14 will know when they must drop stale temp tables or not. The next task is now modify 4.0.14 to implement this. sql/log.cc: Fix for bug 254 : the first Start_log_event after server startup will have created=now(), whereas the next ones (FLUSH LOGS, auto rotation) will have created=0. Before this, it was always now(). This way, slaves >=4.0.14 will know when they must drop stale temp tables or not. sql/log_event.h: An explanation. sql/sql_class.h: Prototype change (see log.cc).
-
- 05 Jun, 2003 2 commits
- 31 May, 2003 2 commits
- 28 May, 2003 1 commit
-
-
unknown authored
Prevent the InnoDB main thread from hogging CPU if a table lingers in the background drop queue (though it is essentially a bug if a table end up there at all) innobase/srv/srv0srv.c: Prevent the InnoDB main thread from hogging CPU if a table lingers in the background drop queue (though it is essentially a bug if a table end up there at all)
-
- 27 May, 2003 1 commit
-
-
unknown authored
BitKeeper/deleted/.del-internals.texi~62b6f580a41c2a43: Delete: Docs/internals.texi
-
- 26 May, 2003 6 commits
- 23 May, 2003 1 commit
-
-
unknown authored
(this bug was already fixed in 4.0, I just copied and pasted two lines).
-
- 21 May, 2003 2 commits
- 14 May, 2003 4 commits
-
-
unknown authored
-
unknown authored
into narttu.mysql.fi:/my/mysql-3.23
-
unknown authored
Backport from 4.0: We had forgotten to call pthread_mutex_destroy when we free an OS mutex in Unix innobase/os/os0sync.c: Backport from 4.0: We had forgotten to call pthread_mutex_destroy when we free an OS mutex in Unix
-
unknown authored
sql/sql_show.cc: SHOW TABLE STATUS displayed wrong Row_format for myisampack'ed tables.
-
- 07 May, 2003 2 commits
-
-
unknown authored
-
unknown authored
Security patch to remove wrong error when one had a global update/delete privilige and a database specific SELECT privilege. sql/sql_acl.cc: Security patch sql/sql_base.cc: Security patch sql/sql_parse.cc: Security patch tests/grant.pl: Test of security patch tests/grant.res: Test of security patch
-