- 05 Apr, 2006 2 commits
-
-
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.
-
- 04 Apr, 2006 8 commits
-
-
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
-
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/mysql-5.0
-
igor@rurik.mysql.com authored
-
- 03 Apr, 2006 8 commits
-
-
bpontz@shasta.mysql.com authored
-
bar@mysql.com authored
into mysql.com:/usr/home/bar/mysql-5.0
-
bar@mysql.com authored
into mysql.com:/usr/home/bar/mysql-4.1.12076
-
serg@serg.mylan authored
-
kent@mysql.com authored
-
kent@mysql.com authored
Distribute mysql-test-run.pl
-
kent@mysql.com authored
into mysql.com:/Users/kent/mysql/bk/mysql-4.1-new
-
kent@mysql.com authored
Changed web address order.mysql.com to shop.mysql.com
-
- 02 Apr, 2006 1 commit
-
-
kent@mysql.com authored
Install Perl mysql-test-run into test directory
-
- 01 Apr, 2006 13 commits
-
-
igor@rurik.mysql.com authored
Results changed after the bug fix.
-
igor@rurik.mysql.com authored
Multiple equalities were not adjusted after reading constant tables. It resulted in neglecting good index based methods that could be used to access of other tables.
-
kent@mysql.com authored
-
kent@mysql.com authored
Let "make install" install mysql-test-run.pl mysql.spec.sh: Set $LDFLAGS from $MYSQL_BUILD_LDFLAGS (bug#16662)
-
kent@mysql.com authored
into mysql.com:/Users/kent/mysql/bk/mysql-4.1-new
-
kent@mysql.com authored
Typo (bug#17167)
-
kent@mysql.com authored
Use CPPFLAGS when testing to link "libz" found in --with-zlib-dir=, and search the given include directory first (bug#18369)
-
kent@mysql.com authored
into mysql.com:/Users/kent/mysql/bk/mysql-5.0-new
-
kent@mysql.com authored
Use CPPFLAGS when testing to link "libz" found in --with-zlib-dir=, and search the given include directory first (bug#18369)
-
kent@mysql.com authored
into mysql.com:/Users/kent/mysql/bk/mysql-5.0-new
-
kent@mysql.com authored
into mysql.com:/Users/kent/mysql/bk/mysql-5.0-new
-
aivanov@mysql.com authored
into mysql.com:/home/alexi/innodb/mysql-5.0-merged
-
kent@mysql.com authored
Set MYSQL_SERVER_SUFFIX from build scripts, not hard code it into Visual Studio project files, bug#15974
-
- 31 Mar, 2006 6 commits
-
-
kent@mysql.com authored
Enable automake to determine dependency on yaSSL, by explicitly listing the .la files in Makefile.am, instead of using 'yassl_libs_with_path', bug#18273
-
aivanov@mysql.com authored
into mysql.com:/home/alexi/innodb/mysql-5.0-merged
-
aivanov@mysql.com authored
Fixed BUG#15650: DELETE with LEFT JOIN crashes server with innodb_locks_unsafe_for_binlog. Fixed compilation problem with non-C99 compilers in btr0sea.c
-
timour@mysql.com authored
-
timour@mysql.com authored
into mysql.com:/home/timka/mysql/src/5.0-bug-16710
-
timour@mysql.com authored
The bug was due to a missed case in the detection of whether an index can be used for loose scan. More precisely, the range optimizer chose to use loose index scan for queries for which the condition(s) over an index key part could not be pushed to the index together with the loose scan. As a result, loose index scan was selecting the first row in the index with a given GROUP BY prefix, and was applying the WHERE clause after that, while it should have inspected all rows with the given prefix, and apply the WHERE clause to all of them. The fix detects and skips such cases.
-
- 30 Mar, 2006 2 commits
-
-
kent@mysql.com authored
Use when testing if shared library exists, bug#16332
-
igor@rurik.mysql.com authored
into rurik.mysql.com:/home/igor/dev/mysql-5.0-0
-