- 12 Jul, 2005 1 commit
-
-
evgen@moonbone.local authored
New item created in find_field_in_table() to fix view's item, was created without taking into account original item's alias. This patch checks if alias is set to the original item and if so sets it to newly created item.
-
- 04 Jul, 2005 1 commit
-
-
monty@mysql.com authored
Better fix for ON DUPLICATE KEY UPDATE
-
- 03 Jul, 2005 1 commit
-
-
monty@mysql.com authored
-
- 02 Jul, 2005 6 commits
-
-
bell@sanja.is.com.ua authored
-
monty@mysql.com authored
into mysql.com:/home/my/mysql-4.1
-
monty@mysql.com authored
into mysql.com:/home/my/mysql-4.1
-
bell@sanja.is.com.ua authored
-
kent@mysql.com authored
into mysql.com:/Users/kent/mysql/bk/mysql-4.1
-
kent@mysql.com authored
Enable build with CXX=gcc and gcc version 4
-
- 01 Jul, 2005 31 commits
-
-
kent@mysql.com authored
into mysql.com:/Users/kent/mysql/bk/mysql-4.1
-
heikki@hundin.mysql.fi authored
Optimize speed: no need to keep track of set new rec locks in a consistent read
-
heikki@hundin.mysql.fi authored
into hundin.mysql.fi:/home/heikki/mysql-5.0
-
heikki@hundin.mysql.fi authored
Fix another bug in the fix of Bug #3300
-
heikki@hundin.mysql.fi authored
Fix bug in the Bug #3300 bug fix
-
heikki@hundin.mysql.fi authored
Fix Bug #3300 : if innodb_locks_unsafe_for_binlog is set, release locks on rows that we do not UPDATE or DELETE
-
bell@sanja.is.com.ua authored
into sanja.is.com.ua:/home/bell/mysql/bk/work-bug5-4.1
-
bell@sanja.is.com.ua authored
-
svoj@mysql.com authored
into mysql.com:/home/svoj/devel/mysql/yassl1-mysql-5.0
-
pem@mysql.com authored
into mysql.com:/home/pem/work/mysql-5.0
-
konstantin@mysql.com authored
-
svoj@mysql.com authored
Merge with latest yaSSL. It includes fix for bigendian/littleendian problem (fixes func_encrypt test failure). Our trees are in sync now.
-
pem@mysql.com authored
into mysql.com:/home/pem/work/mysql-5.0
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/mysql-5.0
-
pem@mysql.com authored
into mysql.com:/home/pem/work/mysql-5.0
-
konstantin@mysql.com authored
into mysql.com:/opt/local/work/mysql-5.0-11172-new
-
konstantin@mysql.com authored
-
igor@rurik.mysql.com authored
into rurik.mysql.com:/home/igor/mysql-5.0
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/mysql-5.0
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/mysql-4.1
-
msvensson@neptunus.(none) authored
-
pem@mysql.com authored
We want to have the defacto standard syntax for labels ("L:" instead of "label L;"), and fix some known bugs, before we enable this again. The code is left intact (#ifdef'ed SP_GOTO) and the test cases are kept in sp-goto.test, for the future...
-
konstantin@mysql.com authored
Add a test case for Bug#11656 "Server crash with mysql_stmt_fetch (cursors)", the bug itself is no longer present.
-
konstantin@mysql.com authored
-
konstantin@mysql.com authored
into mysql.com:/opt/local/work/mysql-5.0-11172-new
-
konstantin@mysql.com authored
CURSOR_TYPE_READ_ONLY date/datetime filter server crash". The fix adds support for Item_change_list in cursors (proper rollback of the modified item tree).
-
igor@rurik.mysql.com authored
into rurik.mysql.com:/home/igor/dev/mysql-5.0-0
-
bar@mysql.com authored
into mysql.com:/usr/home/bar/mysql-5.0
-
igor@rurik.mysql.com authored
Fixed the results of a test for group_concat. After the fix foor bug #11639 the results became correct. olap.result, olap.test: Added a test case for bug #11639. sql_select.cc: Fixed bug #11639: a wrong result set when using a view instead of the underlying table in a rollup query executed through filesort. The old code did not take into account that we always use an Item_ref object when referring to a view column. item.h: Fixed bug #11639. Now if two Item_ref items ref1 and ref2 refer to the same field then ref1->eq(ref2) returns 1.
-
bell@sanja.is.com.ua authored
-
bar@mysql.com authored
Bug#11657 Creation of secondary index fails: If TINYBLOB key part length is 255, it is equal to field length. For BLOB, unlike for CHAR/VARCHAR, we should keep a non-zero key part length, otherwise "BLOB/TEXT column used in key specification without a key length" error is produced afterwards. type_blob.result, type_blob.test: fixing tests accordinly
-