- 30 Apr, 2005 1 commit
-
-
serg@serg.mylan authored
remove FIX_GCC_LINKING_PROBLEM and -DDEFINE_CXA_PURE_VIRTUAL replace echo in configure.in with AC_MSG_WARN/AC_MSG_ERROR don't set -DUSE_MYSYS_NEW for gcc 2.95 set $USE_MYSYS_NEW even if CXX is g++ yassl bugfixes instantiate all yassl templates explicitly
-
- 29 Apr, 2005 13 commits
-
-
serg@serg.mylan authored
into serg.mylan:/usr/home/serg/Abk/mysql-5.0
-
hf@deer.(none) authored
into deer.(none):/home/hf/work/mysql-5.0.spaerrs
-
hf@deer.(none) authored
-
serg@serg.mylan authored
-
ingo@mysql.com authored
into mysql.com:/home/mydev/mysql-5.0-5000
-
mskold@mysql.com authored
into mysql.com:/usr/local/home/marty/MySQL/mysql-5.0
-
ingo@mysql.com authored
into mysql.com:/home/mydev/mysql-5.0-5000
-
mskold@mysql.com authored
into mysql.com:/usr/local/home/marty/MySQL/mysql-5.0
-
mskold@mysql.com authored
into mysql.com:/usr/local/home/marty/MySQL/mysql-5.0
-
mskold@mysql.com authored
-
heikki@hundin.mysql.fi authored
Fix compilation error on Windows in innobase_report_binlog_offset_and_commit()
-
ingo@mysql.com authored
After merge fix.
-
ingo@mysql.com authored
into mysql.com:/home/mydev/mysql-5.0-5000
-
- 28 Apr, 2005 23 commits
-
-
sergefp@mysql.com authored
into mysql.com:/home/psergey/mysql-5.0-bug9821
-
ingo@mysql.com authored
into mysql.com:/home/mydev/mysql-5.0-5000
-
sergefp@mysql.com authored
into mysql.com:/home/psergey/mysql-5.0-bug9298-merge
-
ingo@mysql.com authored
into mysql.com:/home/mydev/mysql-4.1-4100
-
ingo@mysql.com authored
Changed the creation of the .MRG file so that only the table name is written when the MyISAM table is in the same database as the MERGE table, a relative path is used in other cases in mysqld, and possibly an absolute path is used in an embedded server. No test case is added as the external behaviour is unchanged. Only the file names within the .MRG file are changed.
-
jimw@mysql.com authored
-
ingo@mysql.com authored
Merge from 4.0.
-
ingo@mysql.com authored
This is the second of three changesets. It contains the pure bug fix. It also contains the second after-review fixes. The problem was that with gcc on x86, shifts are done modulo word size. 'value' is 32 bits wide and shifting it by 32 bits is a no-op. This was triggered by an evil distribution of character incidences. A distribution of 2917027827 characters made of 202 distinct values led to 34 occurrences of 32-bit Huffman codes. This might have been the first time ever that write_bits() had to write 32-bit values. Since it can be expected that one day even 32 bits might be insufficient, the third changeset suggests to enlarge some variables to 64 bits.
-
svoj@mysql.com authored
yaSSL-0.9.7 library bundled.
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/mysql-5.0
-
msvensson@neptunus.(none) authored
Setting AC_PREREQ required version to 2.50 until we have sorted out what is required. The manual says 2.58.
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/mysql-5.0
-
msvensson@neptunus.(none) authored
-
konstantin@mysql.com authored
value into a char field": the patch submitted for the bug a while ago has never been reviewed or approved to push into 4.0. Decimal support in 5.0 resolves the issue. Adding the test case and closing the bug report.
-
msvensson@neptunus.(none) authored
-
msvensson@neptunus.(none) authored
-
mskold@mysql.com authored
into mysql.com:/usr/local/home/marty/MySQL/mysql-4.1
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/mysql-4.1
-
msvensson@neptunus.(none) authored
- Remove ha_archive::rename_table and move the fix to handler::rename_table
-
mskold@mysql.com authored
into mysql.com:/usr/local/home/marty/MySQL/mysql-5.0
-
mskold@mysql.com authored
Fix for avoiding gettin Invalid schema object version when doing local changes, more post review fixes
-
mskold@mysql.com authored
-
mskold@mysql.com authored
-
- 27 Apr, 2005 3 commits
-
-
ingo@mysql.com authored
into mysql.com:/home/mydev/mysql-5.0-5000
-
ingo@mysql.com authored
After merge fix.
-
msvensson@neptunus.(none) authored
- Different behaviuor in 5.0 pushes a warning when renaming a non existent file. Avoid that by checking that the file exists before renaming.
-