- 25 Apr, 2006 2 commits
-
-
jonas@perch.ndb.mysql.com authored
into perch.ndb.mysql.com:/home/jonas/src/50-work
-
jonas@perch.ndb.mysql.com authored
Handle early abort of scan, so that resources are correctly freed
-
- 18 Apr, 2006 3 commits
-
-
jonas@perch.ndb.mysql.com authored
post merge
-
jonas@perch.ndb.mysql.com authored
into perch.ndb.mysql.com:/home/jonas/src/50-work
-
jonas@perch.ndb.mysql.com authored
fix api_signal_log print of uncond signals
-
- 10 Apr, 2006 3 commits
-
-
jonas@perch.ndb.mysql.com authored
4.1->5.0 merge
-
jonas@perch.ndb.mysql.com authored
into perch.ndb.mysql.com:/home/jonas/src/50-work
-
jonas@perch.ndb.mysql.com authored
fix correct frag count in Backup block
-
- 07 Apr, 2006 5 commits
-
-
jonas@perch.ndb.mysql.com authored
fix mem leak (not during running of transactions, but a few bytes when shutting down)
-
jonas@perch.ndb.mysql.com authored
silent valgrind warnings 5.0, ndb_autodiscover
-
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/41-work
-
jonas@perch.ndb.mysql.com authored
remove debug prinouts in Qmgr
-
- 06 Apr, 2006 14 commits
-
-
jonas@perch.ndb.mysql.com authored
into perch.ndb.mysql.com:/home/jonas/src/50-work
-
jonas@perch.ndb.mysql.com authored
1) make sure that check_multi_node_shutdown does not proceed (in stop case) 2) Fix printout
-
jonas@perch.ndb.mysql.com authored
-
jonas@perch.ndb.mysql.com authored
add two new start options that will decrease likelyhood of bug#18612 push cntr-sp2 logic down into qmgr-sp1 to decrease likelyhood of bug#18612
-
msvensson@shellback.(none) authored
into shellback.(none):/home/msvensson/mysql/mysql-5.0
-
bar@mysql.com authored
as it is now required by mysql_set_character_set()
-
bar@mysql.com authored
Bug#18830 incompatibility new libraries with old server Additional 5.0 fix: applying the same patch to client.c.
-
bar@mysql.com authored
into mysql.com:/usr/home/bar/mysql-5.0
-
bar@mysql.com authored
Bug#18830: incompatibility new libraries with old server Don't execute SET NAMES with pre-4.1 server.
-
bar@mysql.com authored
into mysql.com:/usr/home/bar/mysql-5.0
-
bar@mysql.com authored
Adding test case to cover queries which worked incorrectly earlier: Bug#18321: Can't store EuroSign with latin1_german1_ci and latin1_general_ci
-
bar@mysql.com authored
Using local.
-
bar@mysql.com authored
into mysql.com:/usr/home/bar/mysql-5.0
-
bar@mysql.com authored
Backporting a 5.0 change: MAX_BUF was too small for Index.xml Changeing MAX_BUF and adding assert to easier catch the same problem in the future. ctype-extra.c: Regenerating ctype-extra.c with the fixed conf_to_src.
-
- 05 Apr, 2006 7 commits
-
-
igor@rurik.mysql.com authored
into rurik.mysql.com:/home/igor/dev/mysql-5.0-0
-
bar@mysql.com authored
Buffer was too small to load Index.xml. So some charsets were not gerenrated. Making the buffer bigger, and adding an DBUG_ASSERT, to easier catch the problem in the future. ctype-extra.c: Additional charsets were generated.
-
jonas@perch.ndb.mysql.com authored
-
evgen@sunlight.local authored
into sunlight.local:/local_work/16281-bug-5.0-mysql
-
evgen@sunlight.local authored
Mutli-table uses temporary table to store new values for fields. With the new values the rowid of the record to be updated is stored in a Field_string field. Table to be updated is set as source table of the rowid field. But when the temporary table creates the tmp field for the rowid field it converts it to a varstring field because the table to be updated was created by the v4.1. Due to this the stored rowids were broken and no records for update were found. The flag can_alter_field_type is added to Field_string class. When it is set to 0 the field won't be converted to varstring. The Field_string::type() function now always returns MYSQL_TYPE_STRING if can_alter_field_type is set to 0. The multi_update::initialize_tables() function now sets can_alter_field_type flag to 0 for the rowid fields denying conversion of the field to a varstring field.
-
jonas@perch.ndb.mysql.com authored
into perch.ndb.mysql.com:/home/jonas/src/50-work
-
msvensson@shellback.(none) authored
into shellback.(none):/home/msvensson/mysql/mysql-5.0
-
- 04 Apr, 2006 6 commits
-
-
igor@rurik.mysql.com authored
The code in opt_sum_query that prevented the COUNT/MIN/MAX optimization from being applied to outer joins was not adjusted after introducing nested joins. As a result if an outer join contained a reference to a view as an inner table the code of opt_sum_query missed the presence of an on expressions and erroneously applied the mentioned optimization.
-
bar@mysql.com authored
into mysql.com:/usr/home/bar/mysql-5.0
-
bar@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
-
tomas@poseidon.ndb.mysql.com authored
-