An error occurred fetching the project authors.
- 20 Dec, 2003 8 commits
-
-
pem@mysql.com authored
into mysql.com:/home/pem/work/mysql-5.0-merge
-
pem@mysql.comhem.se authored
-
pem@mysql.com authored
-
heikki@hundin.mysql.fi authored
Define macro ULINTPF which can be used in printf statements as the print format of ulint both on Win64 and other platforms
-
heikki@hundin.mysql.fi authored
Check at compilation time on Unix that InnoDB ulint is the same size as void*, and also check it at runtime
-
monty@mysql.com authored
-
monty@mysql.com authored
A after merge fix for last merge
-
konstantin@oak.local authored
-
- 19 Dec, 2003 27 commits
-
-
guilhem@mysql.com authored
into mysql.com:/home/mysql_src/mysql-5.0-new-binlog-format
-
guilhem@gbichot2 authored
For previous commit I had run only rpl* tests, here the other ones had a few surprises. Latest status: - all tests pass - all replication tests pass with Valgrind This is the final-final commit & push. Doc remains.
-
konstantin@mysql.com authored
into mysql.com:/home/kostja/mysql/mysql-4.1-prep_st_hack
-
konstantin@oak.local authored
-
guilhem@mysql.com authored
into mysql.com:/home/mysql_src/mysql-5.0-new-binlog-format
-
sergefp@mysql.com authored
into mysql.com:/dbdata/psergey/mysql-5.0-imerge-unique
-
sergefp@mysql.com authored
-
guilhem@gbichot2 authored
* A more dynamic binlog format which allows small changes (1064) * Log session variables in Query_log_event (1063) It contains a few bugfixes (which I made when running the testsuite). I carefully updated the results of the testsuite (i.e. I checked for every one, if the difference between .reject and .result could be explained). Apparently mysql-test-run --manager is broken in 4.1 and 5.0 currently, so I could neither run the few tests which require --manager, nor check that they pass nor modify their .result. But for builds, we don't run with --manager. Apart from --manager, the full testsuite passes, with Valgrind too (no errors). I'm going to push in the next minutes. Remains: update the manual. Note: by chance I saw that (in 4.1, in 5.0) rpl_get_lock fails when run alone; this is normal at it makes assumptions on thread ids. I will fix this one day in 4.1.
-
pem@mysql.comhem.se authored
-
pem@mysql.com authored
-
monty@mysql.com authored
into mysql.com:/my/mysql-4.1
-
pem@mysql.comhem.se authored
-
heikki@hundin.mysql.fi authored
On 64-bit Windows use InnoDB's own printf function where %lu is converted to %I64u; this eliminates Intel compiler warnings on IA64
-
monty@mysql.com authored
-
monty@mysql.com authored
-
konstantin@oak.local authored
All tests pass (client_test included)
-
pem@mysql.com authored
-
konstantin@oak.local authored
-
bar@bar.intranet.mysql.r18.ru authored
into bar.intranet.mysql.r18.ru:/usr/home/bar/mysql-4.1
-
monty@mysql.com authored
-
bar@bar.intranet.mysql.r18.ru authored
"USE db" affected the character set of further CREATE DATABASEs, which should have not happened.
-
monty@mysql.com authored
-
monty@mysql.com authored
-
monty@mysql.com authored
Cleaned up embedded library access and query cache handling Changed min stack size to 128K (to allow longer MyISAM keys) Fixed wrong priority for XOR (should be less than NEG to get -1^1 to work)
-
lenz@mysql.com authored
into mysql.com:/space/my/mysql-4.1
-
lenz@kallisto.local authored
-
ram@gw.mysql.r18.ru authored
-
- 18 Dec, 2003 5 commits
-
-
sergefp@mysql.com authored
-
pem@mysql.comhem.se authored
-
pem@mysql.com authored
-
pem@mysql.comhem.se authored
platforms.
-
monty@mysql.com authored
-