- 27 Mar, 2007 2 commits
-
-
thek@kpdesk.mysql.com authored
into kpdesk.mysql.com:/home/thek/dev/mysql-5.1-runtime
-
thek@kpdesk.mysql.com authored
- 1.84e+15 converted to unsigned bigint should be 18400000000000000000 < 18446744073709551615. - The test will still fail on windows, and is extracted into a new bug report.
-
- 24 Mar, 2007 1 commit
-
-
kostja@bodhi.local authored
-
- 23 Mar, 2007 6 commits
-
-
Kristofer.Pettersson@naruto. authored
into naruto.:C:/cpp/mysql-5.0-runtime
-
Kristofer.Pettersson@naruto. authored
into naruto.:C:/cpp/mysql-5.1-runtime
-
Kristofer.Pettersson@naruto. authored
into naruto.:C:/cpp/mysql-5.1-runtime
-
kostja@bodhi.local authored
to not collide with the recently introduced thread scheduler module.
-
kostja@bodhi.local authored
-
kostja@bodhi.local authored
A larger patch is to come, this is to exclude rudimentary changes from it.
-
- 21 Mar, 2007 7 commits
-
-
kostja@bodhi.local authored
-
kostja@bodhi.local authored
into bodhi.local:/opt/local/work/mysql-5.1-runtime
-
kostja@bodhi.local authored
-
kostja@bodhi.local authored
into bodhi.local:/opt/local/work/mysql-5.1-runtime
-
kostja@bodhi.local authored
into bodhi.local:/opt/local/work/mysql-5.0-runtime
-
kostja@bodhi.local authored
-
kostja@bodhi.local authored
-
- 20 Mar, 2007 2 commits
-
-
Kristofer.Pettersson@naruto. authored
into naruto.:C:/cpp/mysql-5.1-runtime
-
ibabaev@bk-internal.mysql.com authored
into bk-internal.mysql.com:/data0/bk/mysql-5.1-opt
-
- 19 Mar, 2007 7 commits
-
-
evgen@moonbone.local authored
After merge fix.
-
evgen@moonbone.local authored
into moonbone.local:/mnt/gentoo64/work/test-5.1-opt-mysql
-
evgen@moonbone.local authored
Removed wrong fix for the bug#27006. The bug was added by the fix for the bug#19978 and fixed by Monty on 2007/02/21. trigger.test, trigger.result: Corrected test case for the bug#27006.
-
kostja@bodhi.local authored
into bodhi.local:/opt/local/work/mysql-5.1-runtime
-
kostja@bodhi.local authored
into bodhi.local:/opt/local/work/mysql-5.1-runtime
-
kostja@bodhi.local authored
into bodhi.local:/opt/local/work/mysql-5.0-runtime
-
Kristofer.Pettersson@naruto. authored
-
- 17 Mar, 2007 2 commits
-
-
serg@janus.mylan authored
include/config-win.h: SIZEOF_INT include/my_global.h: win64 fix support-files/Makefile.am: automake magic
-
serg@janus.mylan authored
into janus.mylan:/usr/home/serg/Abk/mysql-5.1
-
- 16 Mar, 2007 13 commits
-
-
serg@janus.mylan authored
s/ulonglong/key_part_map/, comments
-
evgen@moonbone.local authored
Post-merge fix.
-
serg@janus.mylan authored
into janus.mylan:/usr/home/serg/Abk/mysql-5.1
-
evgen@moonbone.local authored
into moonbone.local:/mnt/gentoo64/work/test-5.1-opt-mysql
-
serg@janus.mylan authored
-
holyfoot/hf@mysql.com/hfmain.(none) authored
-
holyfoot/hf@hfmain.(none) authored
into mysql.com:/home/hf/work/mrg/mysql-5.1-opt
-
kroki/tomash@moonlight.home authored
Fix three compilation warnings.
-
Kristofer.Pettersson@naruto. authored
into naruto.:C:/cpp/bug20777/my51-bug20777
-
kroki/tomash@moonlight.home authored
into moonlight.home:/home/tomash/src/mysql_ab/mysql-5.1-wl3698
-
kroki/tomash@moonlight.home authored
BUG#26429: SHOW CREATE EVENT is incorrect for an event that STARTS NOW() BUG#26431: Impossible to re-create an event from backup if its STARTS clause is in the past WL#3698: Events: execution in local time zone The problem was that local times specified by the user in AT, STARTS and ENDS of CREATE EVENT/ALTER EVENT statement were converted to UTC, and the original time zone was forgotten. This way, event scheduler couldn't honor Daylight Saving Time shifts, and times shown to the user were also in UTC. Additionally, CREATE EVENT didn't allow times in the past, thus preventing straightforward event restoration from old backups. This patch reworks event scheduler time computations, performing them in the time zone associated with the event. Also it allows times to be in the past. The patch adds time_zone column to mysql.event table. NOTE: The patch is almost final, but the bug#9953 should be pushed first.
-
evgen@moonbone.local authored
UPDATE if the row wasn't actually changed. This bug was caused by fix for bug#19978. It causes AFTER UPDATE triggers not firing if a row wasn't actually changed by the update part of the INSERT .. ON DUPLICATE KEY UPDATE. Now triggers are always fired if a row is touched by the INSERT ... ON DUPLICATE KEY UPDATE.
-
thek@kpdesk.mysql.com authored
into kpdesk.mysql.com:/home/thek/dev/mysql-5.1-runtime
-