- 23 May, 2006 1 commit
-
-
stewart@mysql.com authored
fix display of mgm protocol parser error in mgmapi
-
- 22 May, 2006 1 commit
-
-
stewart@mysql.com authored
into mysql.com:/home/stewart/Documents/MySQL/5.0/main
-
- 21 May, 2006 2 commits
-
-
holyfoot@mysql.com authored
into mysql.com:/home/hf/work/mysql-5.0.mrg
-
pekka@mysql.com authored
-
- 20 May, 2006 4 commits
-
-
kent@mysql.com authored
-
kent@mysql.com authored
into mysql.com:/Users/kent/mysql/bk/mysql-5.0-new
-
kent@mysql.com authored
-
kent@mysql.com authored
Always compile position independent
-
- 19 May, 2006 6 commits
-
-
jimw@mysql.com authored
into mysql.com:/home/jimw/my/mysql-5.0-clean
-
msvensson@devsrv-b.mysql.com authored
into devsrv-b.mysql.com:/users/msvensson/mysql-5.0
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/mysql-4.1
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/mysql-4.1
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/mysql-5.0
-
msvensson@neptunus.(none) authored
- A segfault occured when the function 'kill_server' called 'my_sigset' with signal number 0. 'my_sigset' is a macro which uses 'sigaction' to install the signal handler with an invalid signal number will on most platforms return EINVAL but yields a segfauilt on IRIX 6.5 - The server crash was detected by mysqld_safe and it was restarted although a shutdown was requested. - Semantics of kill_server(0) is not known, leaving it intact
-
- 18 May, 2006 7 commits
-
-
igor@rurik.mysql.com authored
into rurik.mysql.com:/home/igor/mysql-5.0
-
igor@rurik.mysql.com authored
into rurik.mysql.com:/home/igor/dev/mysql-5.0-2
-
jimw@mysql.com authored
The 'decimals' member of Item_func was being improperly initialized, which resulted in improper results when handling large numeric values.
-
evgen@moonbone.local authored
into moonbone.local:/work/19077-bug-5.0-mysql
-
stewart@mysql.com authored
A further reduction in CPU usage by ndb_mgmd with failed data nodes.
-
igor@rurik.mysql.com authored
into rurik.mysql.com:/home/igor/dev/mysql-5.0-2
-
igor@rurik.mysql.com authored
This bug was introduced when the patch resolving the performance problem 17164 was applied. As a result of that modification the not_null_tables attributes were calculated incorrectly for constant OR conditions. This triggered invalid conversion of outer joins into inner joins.
-
- 17 May, 2006 9 commits
-
-
evgen@moonbone.local authored
The convert_constant_item() function converts constant items to ints on prepare phase to optimize execution speed. In this case it tries to evaluate subselect which contains a derived table and is contained in a derived table. All derived tables are filled only after all derived tables are prepared. So evaluation of subselect with derived table at the prepare phase will return a wrong result. A new flag with_subselect is added to the Item class. It indicates that expression which this item represents is a subselect or contains a subselect. It is set to 0 by default. It is set to 1 in the Item_subselect constructor for subselects. For Item_func and Item_cond derived classes it is set after fixing any argument in Item_func::fix_fields() and Item_cond::fix_fields accordingly. The convert_constant_item() function now doesn't convert a constant item if the with_subselect flag set in it.
-
kent@mysql.com authored
into mysql.com:/Users/kent/mysql/bk/mysql-5.0-new
-
joerg@mysql.com authored
-
joerg@mysql.com authored
Fixes bug#19040 "yaSSL does not compile on AIX".
-
holyfoot@mysql.com authored
into mysql.com:/home/hf/work/mysql-5.0.mrg
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/bug18818/my50-bug18818
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/bug18818/my41-bug18818
-
tulin@production.mysql.com authored
into production.mysql.com:/usersnfs/tulin/mysql-4.1
-
igor@rurik.mysql.com authored
The select statement that specified a view could be slightly changed when the view was saved in a frm file. In particular references to an alias name in the HAVING clause could be substituted for the expression named by this alias. This could result in an error message for a query of the form SELECT * FROM <view>. Yet no such message appeared when executing the query specifying the view.
-
- 16 May, 2006 10 commits
-
-
tomas@poseidon.ndb.mysql.com authored
into poseidon.ndb.mysql.com:/home/tomas/mysql-5.0-main
-
tomas@poseidon.ndb.mysql.com authored
into poseidon.ndb.mysql.com:/home/tomas/mysql-5.0-main
-
tomas@poseidon.ndb.mysql.com authored
into poseidon.ndb.mysql.com:/home/tomas/mysql-4.1-main
-
tomas@poseidon.ndb.mysql.com authored
into poseidon.ndb.mysql.com:/home/tomas/mysql-4.1-main
-
tomas@poseidon.ndb.mysql.com authored
into poseidon.ndb.mysql.com:/home/tomas/mysql-5.0
-
tomas@poseidon.ndb.mysql.com authored
ndb: ndb_waiter disconnect/reconnect on get status error
-
tulin@production.mysql.com authored
into production.mysql.com:/usersnfs/tulin/mysql-4.1
-
tulin@production.mysql.com authored
into production.mysql.com:/usersnfs/tulin/mysql-5.0
-
kent@mysql.com authored
into mysql.com:/data0/mysqldev/my/mysql-4.1
-
aelkin@mysql.com authored
into mysql.com:/usr_rh9/home/elkin.rh9/MySQL/Merge/5.0
-