- 25 Apr, 2006 2 commits
-
-
kroki@mysql.com authored
into mysql.com:/home/tomash/src/mysql_ab/mysql-5.0-real
-
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 12 commits
-
-
knielsen@mysql.com authored
into mysql.com:/data0/knielsen/mysql-5.0-mtr-fix
-
knielsen@mysql.com authored
into mysql.com:/usr/local/mysql/mysql-5.0-mtr-fix
-
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.
-
knielsen@mysql.com authored
-
knielsen@mysql.com authored
into mysql.com:/data0/knielsen/mysql-4.1-mtr-fix
-
joerg@mysql.com authored
into mysql.com:/M50/mysql-5.0
-
ramil@production.mysql.com authored
into production.mysql.com:/usersnfs/rkalimullin/4.1.b17896
-
paul@polar.kitebird.com authored
into polar.kitebird.com:/src/extern/MySQL/bk/mysql-5.0
-
paul@polar.kitebird.com authored
into polar.kitebird.com:/src/extern/MySQL/bk/mysql-4.1
-
paul@polar.kitebird.com authored
into polar.kitebird.com:/src/extern/MySQL/bk/mysql-5.0
-
paul@polar.kitebird.com authored
myisam_ftdump options: --help first, then rest in lexical order.
-
- 23 Apr, 2006 11 commits
-
-
aelkin@mysql.com authored
into mysql.com:/usr_rh9/home/elkin.rh9/MySQL/Merge/5.0
-
aelkin@mysql.com authored
into mysql.com:/usr_rh9/home/elkin.rh9/MySQL/Merge/5.0
-
aelkin@mysql.com authored
The fix refines the algorithm of generating DROPs for binlog. Temp tables with common pseudo_thread_id are clustered into one query. Consequently one replication event per pseudo_thread_id is generated.
-
aelkin@mysql.com authored
accounting non-ai32 in tmpkeyval. This changeset is supposed to be specifically for 4.1. Another changeset is going to push into 5.
-
aelkin@mysql.com authored
-
aelkin@mysql.com authored
into mysql.com:/usr_rh9/home/elkin.rh9/MySQL/Merge/5.0
-
aelkin@mysql.com authored
into mysql.com:/usr_rh9/home/elkin.rh9/MySQL/Merge/5.0
-
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
-
aelkin@mysql.com authored
Backporting a changeset made for 5.0. Comments from there: The fix refines the algorithm of generating DROPs for binlog. Temp tables with common pseudo_thread_id are clustered into one query. Consequently one replication event per pseudo_thread_id is generated.
-
aivanov@mysql.com authored
into mysql.com:/home/alexi/innodb/mysql-4.1
-
- 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 13 commits
-
-
joerg@mysql.com authored
into mysql.com:/M50/mysql-5.0
-
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
into rurik.mysql.com:/home/igor/mysql-4.1
-
igor@rurik.mysql.com authored
-
kroki@mysql.com authored
Do not reset value of LAST_INSERT_ID() in sub-statement.
-
joerg@mysql.com authored
into mysql.com:/M50/mysql-5.0
-
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
-
ramil@production.mysql.com authored
into production.mysql.com:/usersnfs/rkalimullin/4.1.b18643
-
tomas@poseidon.ndb.mysql.com authored
-