- 01 Dec, 2006 10 commits
-
-
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.1-runtime
-
kostja@bodhi.local authored
--cursor_protocol": fix a misleading error message in case of SELECT .. INTO.
-
df@kahlann.erinye.com authored
into kahlann.erinye.com:/home/df/mysql/build/mysql-5.1-build
-
gkodinov@dl145s.mysql.com authored
into dl145s.mysql.com:/data0/bk/team_tree_merge/MERGE/mysql-5.1-opt
-
df@kahlann.erinye.com authored
into kahlann.erinye.com:/home/df/mysql/build/mysql-5.1-build
-
df@kahlann.erinye.com authored
into kahlann.erinye.com:/home/df/mysql/build/mysql-5.1-build
-
malff/marcsql@weblab.(none) authored
into weblab.(none):/home/marcsql/TREE/mysql-5.1-11733_topdown
-
malff/marcsql@weblab.(none) authored
Post review changes the --read-only option is not enforced for the slave thread in replication, or for the SUPER user.
-
- 30 Nov, 2006 30 commits
-
-
df@kahlann.erinye.com authored
into kahlann.erinye.com:/home/df/mysql/build/mysql-5.1-build
-
df@kahlann.erinye.com authored
-
monty@hasky.mysql.fi authored
into mysql.com:/home/my/mysql-5.1
-
monty@narttu.mysql.fi authored
into mysql.com:/home/my/mysql-5.1
-
monty@mysql.com/narttu.mysql.fi authored
Marked some functions as noreturn
-
monty@narttu.mysql.fi authored
into mysql.com:/home/my/mysql-5.1
-
kostja@bodhi.local authored
into bodhi.local:/opt/local/work/mysql-5.1-runtime
-
monty@mysql.com/narttu.mysql.fi authored
Fixed new introduced bug in my_time.c
-
monty@mysql.com/narttu.mysql.fi authored
Don't assert if my_thread_end() is called twice (common case)
-
The reason of this valgrind's compaint is not a bug but rather a feature of bitwise ops: for any value of the byte x x | 1 -> 1, and x & 0 -> 0. x, being a null_byte part of record[1] can be left unassigned even after ha_innobase::index_read_idx because the above and still be correct. Addding a check memory upon the invocation of the function can detect this fact long before record[1], old record, is eventually passed to my_write. Fixed with initialization of record[1]'s null_bytes part in open_table_from_share.
-
gkodinov@dl145s.mysql.com authored
into dl145s.mysql.com:/data0/bk/team_tree_merge/MERGE/mysql-5.1-opt
-
gkodinov/kgeorge@macbook.gmz authored
into macbook.gmz:/Users/kgeorge/mysql/work/B11927-5.0-opt
-
gkodinov/kgeorge@macbook.gmz authored
merge fix : removed undeterministic warnings
-
monty@mysql.com/narttu.mysql.fi authored
Fixed compiler warnings (detected by VC++): - Removed not used variables - Added casts - Fixed wrong assignments to bool - Fixed wrong calls with bool arguments - Added missing argument to store(longlong), which caused wrong store method to be called.
-
df@kahlann.erinye.com authored
into kahlann.erinye.com:/home/df/mysql/build/mysql-5.1-build
-
df@kahlann.erinye.com authored
into kahlann.erinye.com:/home/df/mysql/build/mysql-5.0-build-work
-
df@kahlann.erinye.com authored
-
gkodinov@dl145s.mysql.com authored
into dl145s.mysql.com:/data0/bk/team_tree_merge/MERGE/mysql-5.1-opt
-
gkodinov@dl145s.mysql.com authored
into dl145s.mysql.com:/data0/bk/team_tree_merge/MERGE/mysql-5.1-opt
-
gkodinov@dl145s.mysql.com authored
into dl145s.mysql.com:/data0/bk/team_tree_merge/MERGE/mysql-5.0-opt
-
gkodinov@dl145s.mysql.com authored
into dl145s.mysql.com:/data0/bk/team_tree_merge/MERGE/mysql-5.0-opt
-
gkodinov@dl145s.mysql.com authored
into dl145s.mysql.com:/data0/bk/team_tree_merge/MERGE/mysql-4.1-opt
-
gkodinov/kgeorge@macbook.gmz authored
disabled warnings because their order is undeterministic
-
joerg@trift2. authored
into trift2.:/MySQL/M51/bug24182-5.1
-
joerg@trift2. authored
-
joerg@trift2. authored
into trift2.:/MySQL/M51/push-5.1
-
anozdrin/alik@booka. authored
- BUG#22306: STOP INSTANCE can not be applied for instances in Crashed, Failed and Abandoned; - BUG#23476: DROP INSTANCE does not work - BUG#23215: STOP INSTANCE takes too much time BUG#22306: The problem was that STOP INSTANCE checked that mysqld is up and running. If it was not so, STOP INSTANCE reported an error. Now, STOP INSTANCE reports an error if the instance has been started (mysqld can be down). BUG#23476: The problem was that DROP INSTANCE tried to stop inactive instance. The fix is trivial. BUG#23215: The problem was that locks were not acquired properly, so the instance-monitoring thread could not acquire the mutex, holded by the query-processing thread. The fix is to simplify locking scheme by moving instance-related information to Instance-class out of Guardian-class. This allows to get rid of storing a separate list of Instance-information in Guardian and keeping it synchronized with the original list in Instance_map.
-
monty@hasky.mysql.fi authored
into mysql.com:/home/my/mysql-5.1
-
monty@mysql.com/narttu.mysql.fi authored
- Removed not used variables - Changed some ulong parameters/variables to ulonglong (possible serious bug) - Added casts to get rid of safe assignment from longlong to long (and similar) - Added casts to function parameters - Fixed signed/unsigned compares - Added some constructores to structures - Removed some not portable constructs Better fix for bug Bug #21428 "skipped 9 bytes from file: socket (3)" on "mysqladmin shutdown" (Added new parameter to net_clear() to define when we want the communication buffer to be emptied)
-
baker@bk-internal.mysql.com authored
into bk-internal.mysql.com:/data0/bk/mysql-5.1-arch
-