- 07 May, 2006 1 commit
-
-
sergefp@mysql.com authored
-
- 06 May, 2006 12 commits
-
-
sergefp@mysql.com authored
into mysql.com:/home/psergey/mysql-5.0-bug16798-merge
-
kroki@mysql.com authored
into mysql.com:/home/tomash/src/mysql_ab/mysql-5.0-merge
-
kroki@mysql.com authored
into mysql.com:/home/tomash/src/mysql_ab/mysql-4.1-bug16501
-
kroki@mysql.com authored
into mysql.com:/home/tomash/src/mysql_ab/mysql-4.1-bug16501
-
kroki@mysql.com authored
-
ingo@mysql.com authored
into mysql.com:/home/mydev/mysql-4.1-bug10405
-
ingo@mysql.com authored
into mysql.com:/home/mydev/mysql-5.0-bug10405
-
sergefp@mysql.com authored
into mysql.com:/home/psergey/mysql-5.0-bug16798-merge
-
sergefp@mysql.com authored
The bug was as follows: When merge_key_fields() encounters "t.key=X OR t.key=Y" it will try to join them into ref_or_null access via "t.key=X OR NULL". In order to make this inference it checks if Y<=>NULL, ignoring the fact that value of Y may be not yet known. The fix is that the check if Y<=>NULL is made only if value of Y is known (i.e. it is a constant). TODO: When merging to 5.0, replace used_tables() with const_item() everywhere in merge_key_fields().
-
kroki@mysql.com authored
after merge. Concurrent read and update of privilege structures (like simultaneous run of SHOW GRANTS and ADD USER) could result in server crash. Ensure that proper locking of ACL structures is done. No test case is provided because this bug can't be reproduced deterministically.
-
kroki@mysql.com authored
into mysql.com:/home/tomash/src/mysql_ab/mysql-5.0-merge
-
kroki@mysql.com authored
into mysql.com:/home/tomash/src/mysql_ab/mysql-5.0-real
-
- 05 May, 2006 6 commits
-
-
jani@hundin.mysql.fi authored
into hundin.mysql.fi:/home/jani/mysql-5.0merge_4_1_2nd
-
jani@hundin.mysql.fi authored
into hundin.mysql.fi:/home/jani/mysql-5.0merge_4_1_2nd
-
pekka@mysql.com authored
into mysql.com:/space/pekka/ndb/version/my50-work
-
kroki@mysql.com authored
into mysql.com:/home/tomash/src/mysql_ab/mysql-4.1-bug16372
-
kroki@mysql.com authored
into mysql.com:/home/tomash/src/mysql_ab/mysql-4.1-bug16372
-
kroki@mysql.com authored
into mysql.com:/home/tomash/src/mysql_ab/mysql-4.1-bug16501
-
- 04 May, 2006 21 commits
-
-
pekka@mysql.com authored
-
monty@mysql.com authored
into mysql.com:/home/my/mysql-5.0
-
jani@ua141d10.elisa.omakaista.fi authored
-
jani@ua141d10.elisa.omakaista.fi authored
into ua141d10.elisa.omakaista.fi:/home/my/bk/mysql-5.0
-
paul@polar.kitebird.com authored
Delete: Docs/changelog-5.0.xml
-
paul@polar.kitebird.com authored
into polar.kitebird.com:/src/extern/MySQL/bk/mysql-4.1
-
paul@polar.kitebird.com authored
Delete: Docs/changelog-4.1.xml
-
paul@polar.kitebird.com authored
into polar.kitebird.com:/src/extern/MySQL/bk/mysql-4.1
-
paul@polar.kitebird.com authored
Delete: Docs/changelog-4.0.xml
-
monty@mysql.com authored
into mysql.com:/home/my/mysql-5.0
-
jani@ua141d10.elisa.omakaista.fi authored
into ua141d10.elisa.omakaista.fi:/home/my/bk/mysql-4.1
-
monty@mysql.com authored
mysql-test-run now fails in case of warnings
-
jani@hundin.mysql.fi authored
into hundin.mysql.fi:/home/jani/mysql-5.0merge_4_1
-
jani@ua141d10.elisa.omakaista.fi authored
-
jani@ua141d10.elisa.omakaista.fi authored
TIME_FORMAT using "%l:%i" returns 36:00 with 24:00:00 in TIME column
-
jani@ua141d10.elisa.omakaista.fi authored
-
monty@mysql.com authored
into mysql.com:/home/my/mysql-5.0
-
jani@ua141d10.elisa.omakaista.fi authored
into ua141d10.elisa.omakaista.fi:/home/my/bk/mysql-5.0
-
into a193-229-222-105.elisa-laajakaista.fi:/home/my/bk/mysql-4.1
-
kroki@mysql.com authored
into mysql.com:/home/tomash/src/mysql_ab/mysql-4.1-bug16372
-
kroki@mysql.com authored
into mysql.com:/home/tomash/src/mysql_ab/mysql-4.1-bug16501
-