- 13 Jul, 2005 22 commits
-
-
konstantin@mysql.com authored
into mysql.com:/opt/local/work/mysql-5.0-root
-
konstantin@mysql.com authored
into mysql.com:/opt/local/work/mysql-4.1-11458
-
konstantin@mysql.com authored
data": remove the fix for another bug (8807) that added OUTER_REF_TABLE_BIT to all subqueries that used a placeholder to prevent their evaluation at prepare. As this bit hanged in Item_subselect::used_tables_cache for ever, a constant subquery with a placeholder was never evaluated as such, which caused wrong choice of the execution plan for the statement. - to fix Bug#8807 backport a better fix from 5.0 - post-review fixes.
-
dlenev@mysql.com authored
into mysql.com:/home/dlenev/src/mysql-5.0-mysqlproc
-
dlenev@mysql.com authored
indirectly using non-cached function".
-
mats@mysql.com authored
into mysql.com:/home/bk/bXXX-mysql-5.0
-
mats@mysql.com authored
end of the test, causing subsequent tests to fail.
-
gluh@eagle.intranet.mysql.r18.ru authored
-
dlenev@mysql.com authored
into mysql.com:/home/dlenev/src/mysql-5.0-mysqlproc
-
gluh@mysql.com authored
into mysql.com:/home/gluh/MySQL/Merge/5.0
-
tomas@poseidon.ndb.mysql.com authored
into poseidon.ndb.mysql.com:/home/tomas/mysql-5.0
-
tomas@poseidon.ndb.mysql.com authored
-
dlenev@mysql.com authored
of stored routines definitions even if we already have some tables open and locked. To avoid deadlocks in this case we have to put certain restrictions on locking of mysql.proc table. This allows to use stored routines safely under LOCK TABLES without explicitly mentioning mysql.proc in the list of locked tables. It also fixes bug #11554 "Server crashes on statement indirectly using non-cached function".
-
gluh@eagle.intranet.mysql.r18.ru authored
added out of range handling
-
gluh@eagle.intranet.mysql.r18.ru authored
-
ramil@mysql.com authored
-
lars@mysql.com authored
-
lars@mysql.com authored
into mysql.com:/home/bk/mysql-5.0
-
kent@mysql.com authored
-
evgen@moonbone.local authored
into moonbone.local:/work/mysql-5.0-bug-11709
-
lars@mysql.com authored
into mysql.com:/home/bk/mysql-5.0
-
evgen@moonbone.local authored
Fix for test case for bug#11709
-
- 12 Jul, 2005 18 commits
-
-
evgen@moonbone.local authored
-
evgen@moonbone.local authored
When searching column to sort on, item was compared to field under view column, but not the column itself. Because names of view column and underlaid field may differ, it leads to possibly choosing wrong column for sorting on. This patch makes Item_direct_view_ref::eq(Item *item,...) compare item's name with it's own name proir to comparing to *ref item.
-
lars@mysql.com authored
into mysql.com:/home/bk/mysql-5.0
-
igor@igor-inspiron.creware.com authored
into igor-inspiron.creware.com:/home/igor/mysql-5.0
-
joerg@mysql.com authored
into mysql.com:/M50/mysql-5.0
-
igor@igor-inspiron.creware.com authored
Expanded the test case for bug #6120 to cover DROP VIEW / CREATE VIEW scenario. sql_view.cc: Expanded the fix for bug #6120 to cover the case of DROP VIEW / CREATE_VIEW.
-
igor@igor-inspiron.creware.com authored
into igor-inspiron.creware.com:/home/igor/mysql-5.0
-
joerg@mysql.com authored
into mysql.com:/M50/mysql-5.0
-
sergefp@mysql.com authored
into mysql.com:/home/psergey/mysql-5.0-bug11821-merge
-
sergefp@mysql.com authored
-
evgen@moonbone.local authored
-
evgen@moonbone.local authored
New item created in find_field_in_table() to fix view's item, was created without taking into account original item's alias. This patch checks if alias is set to the original item and if so sets it to newly created item.
-
reggie@linux.site authored
-
jimw@mysql.com authored
into mysql.com:/home/jimw/my/mysql-4.1-clean
-
jimw@mysql.com authored
into mysql.com:/home/jimw/my/mysql-4.1-clean
-
lars@mysql.com authored
into mysql.com:/home/bk/b6987-mysql-4.1
-
joerg@mysql.com authored
into mysql.com:/M41/mysql-4.1
-
lars@mysql.com authored
into mysql.com:/home/bk/b6987-mysql-4.1
-