- 07 Apr, 2008 1 commit
-
-
iggy@slim. authored
-
- 27 Mar, 2008 8 commits
-
-
tnurnberg@white.intern.koehntopp.de authored
into mysql.com:/misc/mysql/mysql-5.0-opt
-
gshchepa/uchum@host.loc authored
into host.loc:/home/uchum/work/5.0-opt
-
joerg@trift2. authored
into trift2.:/MySQL/M50/push-5.0
-
df@pippilotta.erinye.com authored
-
gshchepa/uchum@host.loc authored
into host.loc:/home/uchum/work/5.0-opt
-
gshchepa/uchum@host.loc authored
into host.loc:/home/uchum/work/5.0-opt
-
joerg@trift2. authored
into trift2.:/MySQL/M50/push-5.0
-
tsmith@rhel5-ia64-a.mysql.com authored
into rhel5-ia64-a.mysql.com:/data0/tsmith/build/50
-
- 26 Mar, 2008 6 commits
-
-
gshchepa/uchum@host.loc authored
into host.loc:/home/uchum/work/5.0-opt
-
gshchepa/uchum@host.loc authored
View definition as SELECT ... FROM DUAL WHERE ... has valid syntax, but use of such view in SELECT or SHOW CREATE VIEW syntax causes unexpected syntax error. Server omits FROM DUAL clause when storing view body string in a .frm file for further evaluation. However, syntax of SELECT-witout-FROM query is more restrictive than SELECT FROM DUAL syntax, and doesn't allow the WHERE clause. NOTE: this syntax difference is not documented. View registration procedure has been modified to preserve original structure of view's body.
-
cmiller@zippy.cornsilk.net authored
into zippy.cornsilk.net:/home/cmiller/work/mysql/mysql-5.0-build
-
istruewing@stella.local authored
into stella.local:/home2/mydev/mysql-5.0-axmrg
-
istruewing@stella.local authored
into stella.local:/home2/mydev/mysql-5.0-axmrg
-
istruewing@stella.local authored
into stella.local:/home2/mydev/mysql-5.0-axmrg
-
- 25 Mar, 2008 5 commits
-
-
malff@lambda.hsd1.co.comcast.net. authored
instructions) This bug can not be reproduced in the current version, adding the test case to the test suite for coverage, no code change.
-
gshchepa/uchum@host.loc authored
Minor test case cleanup after bug#34529.
-
joerg@trift2. authored
into trift2.:/MySQL/M50/push-5.0
-
anozdrin/alik@quad.opbmk authored
into quad.opbmk:/mnt/raid/alik/MySQL/devel/5.0-rt-merged
-
svoj@mysql.com/june.mysql.com authored
localhost/default port When creating federated table that points to unspecified host or localhost on unspecified port or port is 0, small memory leak occurs. This happens because we make a copy of unix socket path, which is never freed. With this fix we do not make a copy of unix socket path, instead share->socket points to MYSQL_UNIX_ADDR constant directly. This fix is covered by a test case for BUG34788. Affects 5.0 only.
-
- 24 Mar, 2008 1 commit
-
-
mhansson/autopush@riffraff.(none) authored
into riffraff.(none):/data0/autopush/my50-bug34529
-
- 23 Mar, 2008 1 commit
-
-
holyfoot/hf@hfmain.(none) authored
into mysql.com:/home/hf/work/33334/my50-33334
-
- 22 Mar, 2008 2 commits
-
-
kent@kent-amd64.(none) authored
into mysql.com:/home/kent/bk/build/mysql-5.0-build
-
kent@mysql.com/kent-amd64.(none) authored
into mysql.com:/home/kent/bk/build/mysql-4.1-build
-
- 21 Mar, 2008 2 commits
-
-
gkodinov/kgeorge@magare.gmz authored
into magare.gmz:/home/kgeorge/mysql/autopush/B26461-5.0-opt
-
gkodinov/kgeorge@macbook.gmz authored
The bool data type was redefined to BOOL (4 bytes on windows). Removed the #define and fixed some of the warnings that were uncovered by this. Note that the fix also disables 2 warnings : 4800 : 'type' : forcing value to bool 'true' or 'false' (performance warning) 4805: 'operation' : unsafe mix of type 'type' and type 'type' in operation These warnings will be handled in a separate bug, as they are performance related or bogus. Fixed to int the return type of functions that return more than 2 distinct values.
-
- 20 Mar, 2008 3 commits
-
-
svoj@mysql.com/june.mysql.com authored
correctly - crashes server ! Creating federated table with connect string containing empty (zero-length) host name and port is evaluated as 0 (port is incorrect, omitted or 0) crashes server. This happens because federated calls strcmp() with NULL pointer. Fixed by avoiding strcmp() call if hostname is set to NULL.
-
istruewing@stella.local authored
into stella.local:/home2/mydev/mysql-5.0-axmrg
-
istruewing@stella.local authored
into stella.local:/home2/mydev/mysql-5.0-axmrg
-
- 19 Mar, 2008 11 commits
-
-
cmiller@zippy.cornsilk.net authored
-
cmiller@zippy.cornsilk.net authored
isn't running Pass the process id of the manager as a parameter to "wait_for_pid" and if the manager isn't running, then do not continue to wait. Also, capture the error message of our process-existence test, "kill -0", as we expect errors and shouldn't pass them to the user. Additionally, be a bit more descriptive of what the problem is.
-
tsmith@ramayana.hindu.god authored
into ramayana.hindu.god:/home/tsmith/m/bk/build/50
-
gshchepa/uchum@host.loc authored
into host.loc:/home/uchum/work/5.0-opt
-
tsmith@ramayana.hindu.god authored
into ramayana.hindu.god:/home/tsmith/m/bk/build/50
-
joerg@trift2. authored
into trift2.:/MySQL/M50/push-5.0
-
joerg@trift2. authored
into trift2.:/MySQL/M50/man8-5.0
-
joerg@trift2. authored
into trift2.:/MySQL/M41/push-4.1
-
joerg@trift2. authored
-
davi@mysql.com/endora.local authored
The problem is that unimplemented WIN32 version of pthread_kill is returning ESRCH no matter the arguments, causing calls to mysqld_list_processes to set the procinfo to dead because pthread_kill returns non zero. The dead procinfo would show up on a second invocation of show processlist.
-
joerg@trift2. authored
into trift2.:/MySQL/M41/push-4.1
-