- 15 Aug, 2006 1 commit
-
-
joerg@trift2. authored
-
- 14 Aug, 2006 13 commits
-
-
brian@zim.(none) authored
-
brian@zim.(none) authored
into zim.(none):/home/brian/mysql/dep-5.1
-
kostja@bodhi.local authored
into bodhi.local:/opt/local/work/mysql-5.1-runtime-merge
-
joerg@trift2. authored
-
brian@zim.(none) authored
into zim.(none):/home/brian/mysql/dep-5.0
-
kostja@bodhi.local authored
-
kostja@bodhi.local authored
-
svoj@may.pils.ru authored
into may.pils.ru:/home/svoj/devel/mysql/BUG18874/mysql-5.0
-
kostja@bodhi.local authored
into bodhi.local:/opt/local/work/mysql-5.1-runtime-merge
-
kostja@bodhi.local authored
-
svoj@may.pils.ru authored
Fixed by moving update_key_parts() down to be after write_index().
-
brian@zim.(none) authored
Fix for bug#20648 We introduce a new field method for knowing "real size", and we now in archive null unused bits of a row to null before writing.
-
kostja@bodhi.local authored
-
- 12 Aug, 2006 1 commit
-
-
kostja@bodhi.local authored
into bodhi.local:/opt/local/work/mysql-5.1-runtime-merge
-
- 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 13 commits
-
-
pgalbraith/patg@govinda.patg.net authored
into govinda.patg.net:/home/patg/mysql-build/mysql-5.1-engines-merge
-
patg@govinda.patg.net authored
into govinda.patg.net:/home/patg/mysql-build/mysql-5.1-engines-merge
-
cmiller@zippy.cornsilk.net authored
-
kroki/tomash@moonlight.intranet authored
into moonlight.intranet:/home/tomash/src/mysql_ab/mysql-5.1-runtine-merge
-
kroki/tomash@moonlight.intranet authored
into moonlight.intranet:/home/tomash/src/mysql_ab/mysql-5.1-merge
-
kroki/tomash@moonlight.intranet authored
into moonlight.intranet:/home/tomash/src/mysql_ab/mysql-5.1-merge
-
serg@janus.mylan authored
into janus.mylan:/usr/home/serg/Abk/m51
-
andrey@example.com authored
how did it get in?!? (it's only in local csets so no other tree is affected)
-
andrey@example.com authored
-
serg@janus.mylan authored
into janus.mylan:/usr/home/serg/Abk/m51
-
kroki/tomash@moonlight.intranet authored
into moonlight.intranet:/home/tomash/src/mysql_ab/mysql-5.1-merge
-
cmiller@zippy.cornsilk.net authored
-
cmiller@zippy.cornsilk.net authored
into zippy.cornsilk.net:/home/cmiller/work/mysql/mysql-5.0
-
- 09 Aug, 2006 9 commits
-
-
evgen@moonbone.local authored
After merge fix
-
andrey@lmy004. authored
into lmy004.:/work/mysql-5.1-runtime
-
andrey@lmy004. authored
create function func() returns char(10) binary ... is no more possible. This will be reenabled when bug 2676 "DECLARE can't have COLLATE clause in stored procedure" is fixed. Fix after 2nd review
-
kroki/tomash@moonlight.intranet authored
into moonlight.intranet:/home/tomash/src/mysql_ab/mysql-5.1-rt-merge
-
kroki/tomash@moonlight.intranet authored
-
kroki/tomash@moonlight.intranet authored
into moonlight.intranet:/home/tomash/src/mysql_ab/mysql-5.1-merge
-
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 1 commit
-
-
evgen@sunlight.local authored
into sunlight.local:/local_work/leak_fix-5.1-mysql
-