- 18 Mar, 2006 1 commit
-
-
kent@mysql.com authored
-
- 17 Mar, 2006 6 commits
-
-
cmiller@calliope.local authored
into calliope.local:/Volumes/Source/src/mysql-5.0__bug15846
-
cmiller@calliope.local authored
-
kent@mysql.com authored
NDB_VERSION_BUILD has to be numeric
-
kent@mysql.com authored
Changed release name to 5.0.19a ha_innodb.cc: InnoDB used table locks (not row locks) within stored functions. (Bug #18077)
-
elliot@mysql.com authored
into mysql.com:/home/emurphy/src/mysql/bk-clean/mysql-5.0
-
elliot@mysql.com authored
to binlog too much. When InnoDB has to rollback a transaction because the lock table has filled up, it also needs to inform the upper layer that the transaction was rolled back so that the cached transaction is not written to the binary log.
-
- 16 Mar, 2006 6 commits
-
-
bell@production.mysql.com authored
into production.mysql.com:/usersnfs/abelkin/work-qc-5.0
-
knielsen@mysql.com authored
into mysql.com:/usr/local/mysql/mysql-5.0
-
knielsen@mysql.com authored
-
acurtis@xiphis.org authored
into xiphis.org:/home/antony/work2/p1-bug14575.1
-
msvensson@shellback.(none) authored
into shellback.(none):/home/msvensson/mysql/mysql-5.0
-
acurtis@xiphis.org authored
¨MySQL server crashes if you try to access to InnoDB table¨ crash caused by schizophrenic mysqld - 2 memory locations for logically same function with conflicting values. Fixed by backporting from 5.1 changes to have_xyz_db declarations.
-
- 15 Mar, 2006 1 commit
-
-
bell@book.local authored
because it can couse problem with Query cache (BUG#14767)
-
- 14 Mar, 2006 5 commits
-
-
paul@kite-hub.kitebird.com authored
into kite-hub.kitebird.com:/src/extern/MySQL/bk/mysql-5.0-r1.2084
-
paul@kite-hub.kitebird.com authored
Backport option description change from 5.1 to 5.0.
-
evgen@sunlight.local authored
Afterfix for bug#17366: Unchecked Item_int results in server crash
-
msvensson@shellback.(none) authored
- Add HAVE_OPENSSL and HAVE_YASSL to config-win.h
-
evgen@sunlight.local authored
into sunlight.local:/work_local/17336-bug-5.0-mysql
-
- 13 Mar, 2006 11 commits
-
-
evgen@sunlight.local authored
When there is conjunction of conds, the substitute_for_best_equal_field() will call the eliminate_item_equal() function in loop to build final expression. But if eliminate_item_equal() finds that some cond will always evaluate to 0, then that cond will be substituted by Item_int with value == 0. In this case on the next iteration eliminate_item_equal() will get that Item_int and treat it as Item_cond. This is leads to memory corruption and server crash on cleanup phase. To the eliminate_item_equal() function was added DBUG_ASSERT for checking that all items treaten as Item_cond are really Item_cond. The substitute_for_best_equal_field() now checks that if eliminate_item_equal() returns Item_int and it's value is 0 then this value is returned as the result of whole conjunction.
-
jonas@perch.ndb.mysql.com authored
into perch.ndb.mysql.com:/home/jonas/src/mysql-5.0
-
jonas@perch.ndb.mysql.com authored
into perch.ndb.mysql.com:/home/jonas/src/mysql-4.1
-
jonas@perch.ndb.mysql.com authored
into perch.ndb.mysql.com:/home/jonas/src/50-work
-
jonas@perch.ndb.mysql.com authored
into perch.ndb.mysql.com:/home/jonas/src/mysql-4.1
-
jonas@perch.ndb.mysql.com authored
ndb crash if trigger record get to big, fix incorrect max size of trigger record
-
jonas@perch.ndb.mysql.com authored
into perch.ndb.mysql.com:/home/jonas/src/mysql-5.0
-
jonas@perch.ndb.mysql.com authored
ndb crash if trigger record get to big, fix incorrect max size of trigger record
-
msvensson@shellback.(none) authored
into shellback.(none):/home/msvensson/mysql/mysql-5.0
-
msvensson@shellback.(none) authored
-
msvensson@shellback.(none) authored
-
- 11 Mar, 2006 2 commits
-
-
aelkin@mysql.com authored
into mysql.com:/usr_rh9/home/elkin.rh9/MySQL/FIXES/5.0.20-bug15101-sysdate
-
kent@mysql.com authored
into mysql.com:/Users/kent/mysql/bk/mysql-5.0-new
-
- 10 Mar, 2006 8 commits
-
-
ingo@mysql.com authored
into mysql.com:/home/mydev/mysql-4.1-bug14980
-
ingo@mysql.com authored
into mysql.com:/home/mydev/mysql-5.0-bug14980
-
joerg@mysql.com authored
-
anozdrin@mysql.com authored
Now DEFINER-clause in stored routines is expected to appear in 5.0.20 release, not in 5.0.19. as it was supposed before.
-
joerg@mysql.com authored
into mysql.com:/M50/merge-5.0
-
joerg@mysql.com authored
-
joerg@mysql.com authored
Fixes bug#15861
-
aelkin@mysql.com authored
into mysql.com:/usr_rh9/home/elkin.rh9/MySQL/FIXES/5.0.20-bug15101-sysdate
-