- 25 Apr, 2006 1 commit
-
-
konstantin@mysql.com authored
supported in SP but not in PS": just enable them in prepared statements, the supporting functionality was implemented when they were enabled in stored procedures.
-
- 24 Apr, 2006 2 commits
-
-
dlenev@mysql.com authored
into mysql.com:/home/dlenev/mysql-5.0-bg11081
-
dlenev@mysql.com authored
trigger fails". In cases when CONVERT_TZ() function was used in trigger or stored function (or in stored procedure which was called from trigger or stored function) error about non existing '.' table was reported. Statements that use CONVERT_TZ() function should have time zone related tables in their table list. tz_init_table_list() function which is used to produce part of table list containing those tables didn't set TABLE_LIST::db_length/table_name_length members properly. As result time zone tables needed for CONVERT_TZ() function were incorrectly handled by prelocking algorithm and "Table '.' doesn't exist' error was emitted. This fix changes tz_init_table_list() in such way that it properly inits TABLE_LIST::table_name_length/db_length members and thus produces table list which can be handled by prelocking algorithm correctly.
-
- 23 Apr, 2006 2 commits
-
-
konstantin@mysql.com authored
into mysql.com:/opt/local/work/mysql-5.0-runtime-merge
-
aivanov@mysql.com authored
into mysql.com:/home/alexi/innodb/mysql-5.0
-
- 22 Apr, 2006 2 commits
-
-
dlenev@mysql.com authored
into mysql.com:/home/dlenev/mysql-5.0-bg15153-2
-
dlenev@mysql.com authored
Error was emitted when one tried to select information from view which used merge algorithm and which also had CONVERT_TZ() function in its select list. This bug was caused by wrong assumption that global table list for view which is handled using merge algorithm begins from tables belonging to the main select of this view. Nowadays the above assumption is not true only when one uses convert_tz() function in view's select list, but in future other cases may be added (for example we may support merging of views with subqueries in select list one day). Relying on this false assumption led to the usage of wrong table list for field lookups and therefor errors. With this fix we explicitly use pointer to the beginning of main select's table list.
-
- 21 Apr, 2006 16 commits
-
-
kent@mysql.com authored
Make InnoDB option "loose", as the server might be started with this option just to find out the test is to be skipped in the configuration (bug#17359)
-
kent@mysql.com authored
-
igor@rurik.mysql.com authored
into rurik.mysql.com:/home/igor/mysql-5.0
-
tomas@poseidon.ndb.mysql.com authored
into poseidon.ndb.mysql.com:/home/tomas/mysql-5.0
-
igor@rurik.mysql.com authored
-
kroki@mysql.com authored
Do not reset value of LAST_INSERT_ID() in sub-statement.
-
pem@mysql.com authored
Fixed windows compile error in sql/sp.cc (missing cast to byte*)
-
tomas@poseidon.ndb.mysql.com authored
into poseidon.ndb.mysql.com:/home/tomas/mysql-5.0
-
tomas@poseidon.ndb.mysql.com authored
-
mskold@mysql.com authored
into mysql.com:/usr/local/home/marty/MySQL/mysql-5.0
-
pem@mysql.com authored
into mysql.com:/extern/mysql/5.0/bug18344/mysql-5.0-runtime
-
mskold@mysql.com authored
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/my50-bug19190
-
igor@rurik.mysql.com authored
into rurik.mysql.com:/home/igor/dev/mysql-5.0-0
-
igor@rurik.mysql.com authored
into rurik.mysql.com:/home/igor/dev/mysql-4.1-0
-
igor@rurik.mysql.com authored
The bug caused wrong result sets for union constructs of the form (SELECT ... ORDER BY order_list1 [LIMIT n]) ORDER BY order_list2. For such queries order lists were concatenated and limit clause was completely neglected.
-
- 20 Apr, 2006 16 commits
-
-
aivanov@mysql.com authored
the innodb-5.0-ss476 snapshot.
-
aivanov@mysql.com authored
Fix BUG#18934: "InnoDB crashes when table uses column like DB_ROW_ID". Also, fix memory leaks in row_create_table_for_mysql() in rare corner cases.
-
aivanov@mysql.com authored
into mysql.com:/home/alexi/innodb/mysql-5.0-work Null-merge.
-
aivanov@mysql.com authored
Fix BUG#16814: "SHOW INNODB STATUS format error in LATEST FOREIGN KEY ERROR section" Add a missing newline to the LAST FOREIGN KEY ERROR section in SHOW INNODB STATUS output. Fix BUG#18934: "InnoDB crashes when table uses column names like DB_ROW_ID". Refuse tables that use reserved column names.
-
mleich@mysql.com authored
Fixes for Bug#12429: Replication tests fail: "Slave_IO_Running" (?) differs related to MySQL 4.1 and Bug#16920 rpl_deadlock_innodb fails in show slave status (reported for MySQL 5.1)
-
pem@mysql.com authored
into mysql.com:/extern/mysql/5.0/bug18949/mysql-5.0-runtime
-
mleich@mysql.com authored
into three.local.lan:/home/matthias/Arbeit/mysql-5.0/src-1
-
mskold@mysql.com authored
into mysql.com:/usr/local/home/marty/MySQL/mysql-5.0
-
mleich@mysql.com authored
into three.local.lan:/home/matthias/Arbeit/mysql-5.0/src-1
-
mskold@mysql.com authored
-
evgen@moonbone.local authored
Remove duplicate test case for bug#14169
-
mleich@production.mysql.com authored
into production.mysql.com:/usersnfs/mleich/src
-
evgen@moonbone.local authored
Clean up test case for bug#14169
-
igor@rurik.mysql.com authored
-
igor@rurik.mysql.com authored
into rurik.mysql.com:/home/igor/dev/mysql-5.0-0
-
igor@rurik.mysql.com authored
into rurik.mysql.com:/home/igor/dev/mysql-5.0-0
-
- 19 Apr, 2006 1 commit
-
-
igor@rurik.mysql.com authored
Temporarily commented out a query from the test case for bug 14169 to make it pass with --ps-protocol.
-