- 14 Aug, 2006 4 commits
-
-
rburnett@production.mysql.com authored
My previous change of replacing the call to sprintf with some memcpy type routines was not correct. This patch reverts that. mysql_client_test.c: reverting my previous change
-
rburnett@bk-internal.mysql.com authored
into bk-internal.mysql.com:/data0/bk/mysql-5.0-kt
-
svoj@may.pils.ru authored
into may.pils.ru:/home/svoj/devel/mysql/BUG18874/mysql-5.0
-
svoj@may.pils.ru authored
Fixed by moving update_key_parts() down to be after write_index().
-
- 11 Aug, 2006 2 commits
-
-
svoj@may.pils.ru authored
-
svoj@may.pils.ru authored
into may.pils.ru:/home/svoj/devel/mysql/BUG7391/mysql-5.0
-
- 10 Aug, 2006 5 commits
-
-
Reggie@xgeek. authored
-
rburnett@bk-internal.mysql.com authored
into bk-internal.mysql.com:/data0/bk/mysql-5.0-kt
-
cmiller@zippy.cornsilk.net authored
-
cmiller@zippy.cornsilk.net authored
-
cmiller@zippy.cornsilk.net authored
into zippy.cornsilk.net:/home/cmiller/work/mysql/mysql-5.0
-
- 09 Aug, 2006 4 commits
-
-
rburnett@bk-internal.mysql.com authored
into bk-internal.mysql.com:/data0/bk/mysql-5.0-kt
-
svoj@may.pils.ru authored
into may.pils.ru:/home/svoj/devel/mysql/BUG20060/mysql-5.0
-
svoj@may.pils.ru authored
Problem described in this bug report affects MyISAM tables only. Running mysqld --flush instructs mysqld to sync all changes to disk after each SQL statement. It worked well for INSERT and DELETE statements, but it did sync for UPDATE only in case if there was index change (change of colum that has an index). If no updated column has an index, data wasn't synced to disk. This fix makes UPDATE statement to sync data to disk even if there is no index change (that is only data change) and mysqld is run with --flush option.
-
evgen@sunlight.local authored
After merge fix
-
- 08 Aug, 2006 5 commits
-
-
evgen@sunlight.local authored
into sunlight.local:/local_work/leak_fix
-
evgen@sunlight.local authored
into sunlight.local:/local_work/leak_fix
-
evgen@sunlight.local authored
Correct memory leak fix
-
gluh@mysql.com/gluh.(none) authored
issue an error in case of DECIMAL(M,N) if N > M
-
gluh@mysql.com/gluh.(none) authored
-
- 07 Aug, 2006 3 commits
-
-
holyfoot/hf@mysql.com/deer.(none) authored
into mysql.com:/home/hf/work/mysql-5.0.clean
-
holyfoot/hf@mysql.com/deer.(none) authored
-
evgen@sunlight.local authored
Memory leak fix
-
- 06 Aug, 2006 3 commits
-
-
evgen@sunlight.local authored
into sunlight.local:/local_work/leak_fix
-
evgen@sunlight.local authored
into sunlight.local:/local_work/leak_fix
-
evgen@sunlight.local authored
Memory leak fix
-
- 05 Aug, 2006 2 commits
-
-
Reggie@xgeek. authored
-
rburnett@production.mysql.com authored
Moving call that processes select results out of the assert
-
- 04 Aug, 2006 3 commits
-
-
rburnett@production.mysql.com authored
into production.mysql.com:/usersnfs/rburnett/mysql-5.0-kt
-
rburnett@production.mysql.com authored
set properly. This patch should fix that. mysqld.cc: Call test_if_case_insensitive in all cases so lower_case_file_system always gets set
-
rburnett@bk-internal.mysql.com authored
into bk-internal.mysql.com:/data0/bk/mysql-5.0-kt
-
- 03 Aug, 2006 9 commits
-
-
kostja@bodhi.local authored
-
kostja@bodhi.local authored
-
rburnett@bk-internal.mysql.com authored
into bk-internal.mysql.com:/data0/bk/mysql-5.0-kt
-
msvensson@neptunus.(none) authored
-
msvensson@neptunus.(none) authored
now takes mbmaxlen into account when calculating max_length of new field.
-
svoj@may.pils.ru authored
into may.pils.ru:/home/svoj/devel/mysql/BUG7391/mysql-4.1
-
msvensson@neptunus.(none) authored
- Backport patch from 5.0
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/mysql-5.0-maint
-
msvensson@neptunus.(none) authored
-