- 16 Jul, 2007 1 commit
-
-
tnurnberg@sin.intern.azundris.com authored
into sin.intern.azundris.com:/home/tnurnberg/27198/41-27198
-
- 13 Jul, 2007 1 commit
-
-
tnurnberg@sin.intern.azundris.com authored
gettimeofday() can fail and presumably, so can time(). Keep an eye on it. Since we have no data on this at all so far, we just retry on failure (and log the event), assuming that this is just an intermittant failure. This might of course hang the threat until we succeed. Once we know more about these failures, an appropriate more clever scheme may be picked (only try so many times per thread, etc., if that fails, return last "good" time() we got or some such). Using sql_print_information() to log as this probably only occurs in high load scenarios where the debug- trace likely is disabled (or might interfere with testing the effect). No test-case as this is a non-deterministic issue.
-
- 09 Jul, 2007 1 commit
-
-
tsmith@sita.local authored
into sita.local:/Users/tsmith/m/bk/maint/41
-
- 07 Jul, 2007 1 commit
-
-
gshchepa/uchum@gleb.loc authored
into gleb.loc:/home/uchum/work/bk/4.1-opt
-
- 06 Jul, 2007 2 commits
-
-
tsmith@sita.local authored
into sita.local:/Users/tsmith/m/bk/maint/41
-
antony@ppcg5.local authored
into anubis.xiphis.org:/usr/home/antony/work/mysql-4.1-engines.merge
-
- 05 Jul, 2007 1 commit
-
-
svoj@mysql.com/june.mysql.com authored
Dropping an user defined function may cause server crash in case this function is still in use by another thread. The problem was that our hash implementation didn't update hash link list properly when hash_update() was called.
-
- 04 Jul, 2007 1 commit
-
-
tsmith@maint1.mysql.com authored
into maint1.mysql.com:/data/localhome/tsmith/bk/maint/41
-
- 03 Jul, 2007 4 commits
-
-
gshchepa/uchum@gleb.loc authored
into gleb.loc:/home/uchum/work/bk/4.1-opt
-
gshchepa/uchum@gleb.loc authored
Test case update for bug #29294.
-
gshchepa/uchum@gleb.loc authored
Windows compilation error fix.
-
gshchepa/uchum@gleb.loc authored
The `SELECT 'r' INTO OUTFILE ... FIELDS ENCLOSED BY 'r' ' statement encoded the 'r' string to a 4 byte string of value x'725c7272' (sequence of 4 characters: r\rr). The LOAD DATA statement decoded this string to a 1 byte string of value x'0d' (ASCII Carriage Return character) instead of the original 'r' character. The same error also happened with the FIELDS ENCLOSED BY clause followed by special characters: 'n', 't', 'r', 'b', '0', 'Z' and 'N'. NOTE 1: This is a result of the undocumented feature: the LOAD DATA INFILE recognises 2-byte input sequences like \n, \t, \r and \Z in addition to documented 2-byte sequences: \0 and \N. This feature should be documented (here backspace character is a default ESCAPED BY character, in the real-life example it may be any ESCAPED BY character). NOTE 2, changed behaviour: Now the `SELECT INTO OUTFILE' statement with the `FIELDS ENCLOSED BY' clause followed by one of: 'n', 't', 'r', 'b', '0', 'Z' or 'N' characters encodes this special character itself by doubling it ('r' --> 'rr'), not by prepending it with an escape character.
-
- 26 Jun, 2007 2 commits
-
-
gshchepa/uchum@gleb.loc authored
Sometimes special 0 ENUM values was ALTERed to normal empty string ENUM values. Special 0 ENUM value has the same string representation as normal ENUM value defined as '' (empty string). The do_field_string function was used to convert ENUM data at an ALTER TABLE request, but this function doesn't care about numerical "indices" of ENUM values, i.e. do_field_string doesn't distinguish a special 0 value from an empty string value. A new copy function called do_field_enum has been added to copy special 0 ENUM values without conversion to an empty string.
-
tsmith@maint1.mysql.com authored
into maint1.mysql.com:/data/localhome/tsmith/bk/maint/41
-
- 25 Jun, 2007 1 commit
-
-
gshchepa/uchum@gleb.loc authored
into gleb.loc:/home/uchum/work/bk/4.1-opt
-
- 23 Jun, 2007 1 commit
-
-
into mysql.com:/home/ram/work/b29079/b29079.4.1
-
- 22 Jun, 2007 1 commit
-
-
Problem: long and long long types mess in a comparison may lead to wrong results on some platforms. Fix: prefer [unsigned] long long as [u]longlong as it's used unconditionally in many places.
-
- 20 Jun, 2007 1 commit
-
-
gkodinov/kgeorge@magare.gmz authored
into magare.gmz:/home/kgeorge/mysql/autopush/B29116-4.1-opt
-
- 19 Jun, 2007 4 commits
-
-
gkodinov/kgeorge@magare.gmz authored
counters from relay Updated the test to return columns vertically.
-
msvensson@pilot.(none) authored
into pilot.(none):/data/msvensson/mysql/mysql-4.1-maint
-
msvensson@pilot.(none) authored
- Add test case for this already existing feature
-
holyfoot/hf@mysql.com/hfmain.(none) authored
we use net->vio in my_net_local_init, but in the my_net_init implementation we set it after the call, so work with unspecified net->vio value
-
- 18 Jun, 2007 6 commits
-
-
tsmith@maint1.mysql.com authored
into maint1.mysql.com:/data/localhome/tsmith/bk/maint/41
-
joerg@trift2. authored
into trift2.:/MySQL/M41/push-4.1
-
df@pippilotta.erinye.com authored
into pippilotta.erinye.com:/shared/home/df/mysql/build/mysql-4.1-build
-
df@pippilotta.erinye.com authored
-
joerg@trift2. authored
into trift2.:/MySQL/M41/push-4.1
-
joerg@trift2. authored
into trift2.:/MySQL/M41/push-4.1
-
- 15 Jun, 2007 1 commit
-
-
istruewing@chilla.local authored
into chilla.local:/home/mydev/mysql-4.1-axmrg
-
- 14 Jun, 2007 2 commits
-
-
joerg@trift2. authored
into trift2.:/MySQL/M41/push-4.1
-
holyfoot/hf@mysql.com/hfmain.(none) authored
into mysql.com:/d2/hf/mrg/mysql-4.1-opt
-
- 13 Jun, 2007 8 commits
-
-
df@pippilotta.erinye.com authored
-
df@pippilotta.erinye.com authored
into pippilotta.erinye.com:/shared/home/df/mysql/build/mysql-4.1-build
-
joerg@trift2. authored
into trift2.:/MySQL/M41/push-4.1
-
joerg@trift2. authored
Improved check for thread identity in the "embedded" case, provided by Monty. This finishes the fixes for bug#27078.
-
df@pippilotta.erinye.com authored
into pippilotta.erinye.com:/shared/home/df/mysql/build/mysql-4.1
-
df@pippilotta.erinye.com authored
into pippilotta.erinye.com:/shared/home/df/mysql/build/mysql-4.1
-
msvensson@pilot.(none) authored
- Make tesingt continue even if test log file does not exists
-
- 12 Jun, 2007 1 commit
-
-
cmiller@zippy.cornsilk.net authored
protocol Fixed duplicated code, same as last commit. One could send a malformed packet that caused the server to SEGV. In recent versions of the password protocol, the client tells the server what length the ciphertext is (almost always 20). If that length was large enough to overflow a signed char, then the number would jump to very large after being casted to unsigned int. Instead, cast the *passwd char to uchar.
-