- 10 Aug, 2007 4 commits
-
-
gshchepa/uchum@gleb.loc authored
into gleb.loc:/home/uchum/work/bk/5.1-opt
-
gshchepa/uchum@gleb.loc authored
into gleb.loc:/home/uchum/work/bk/5.1-opt
-
gshchepa/uchum@gleb.loc authored
into gleb.loc:/home/uchum/work/bk/5.0-opt
-
gshchepa/uchum@gleb.loc authored
into gleb.loc:/home/uchum/work/bk/5.1-opt
-
- 08 Aug, 2007 5 commits
-
-
kostja@bodhi.(none) authored
-
kostja@bodhi.(none) authored
during "CREATE ... LIKE ..." Only affects engine writers. No change in server behaviour.
-
kostja@bodhi.(none) authored
into bodhi.(none):/opt/local/work/mysql-5.1-runtime
-
kostja@bodhi.(none) authored
into bodhi.(none):/opt/local/work/mysql-5.1-runtime
-
kostja@bodhi.(none) authored
into bodhi.(none):/opt/local/work/mysql-5.0-runtime
-
- 06 Aug, 2007 19 commits
-
-
kostja@bodhi.(none) authored
-
-
kostja@bodhi.(none) authored
-
kostja@bodhi.(none) authored
-
kostja@bodhi.(none) authored
-
gkodinov/kgeorge@magare.gmz authored
-
gkodinov/kgeorge@magare.gmz authored
into magare.gmz:/home/kgeorge/mysql/autopush/B29536-5.0-opt
-
gkodinov/kgeorge@magare.gmz authored
into magare.gmz:/home/kgeorge/mysql/work/B29536-5.1-opt
-
gkodinov/kgeorge@magare.gmz authored
MySQL replicates the time zone only when operations that involve it are performed. This is controlled by a flag. But this flag is set only on successful operation. The flag must be set also when there is an error that involves a timezone (so the master would replicate the error to the slaves). Fixed by moving the setting of the flag before the operation (so it apples to errors as well).
-
kostja@bodhi.(none) authored
into bodhi.(none):/opt/local/work/mysql-5.0-runtime
-
kostja@bodhi.(none) authored
VIEW". mysql_list_fields() C API function would incorrectly set MYSQL_FIELD::decimals member for some view columns. The problem was in an incomplete implementation of Item_ident_for_show::make_field(), which is responsible for view columns metadata.
-
igor@olga.mysql.com authored
into olga.mysql.com:/home/igor/mysql-5.1-opt
-
igor@olga.mysql.com authored
a problem for BIT type values different from the one reported for the bug.
-
igor@olga.mysql.com authored
-
kent@kent-amd64.(none) authored
into mysql.com:/home/kent/bk/cmake-tls/mysql-5.1-build-new
-
kent@mysql.com/kent-amd64.(none) authored
Corrected install path
-
kent@mysql.com/kent-amd64.(none) authored
Copy embedded .pdb and static debug lib
-
igor@olga.mysql.com authored
into olga.mysql.com:/home/igor/dev-opt/mysql-5.1-opt-bug30219
-
igor@olga.mysql.com authored
-
- 05 Aug, 2007 12 commits
-
-
kent@kent-amd64.(none) authored
into mysql.com:/home/kent/bk/cmake-tls/mysql-5.1-build-new
-
kent@mysql.com/kent-amd64.(none) authored
Search "relwithdebinfo" directory in CMake Visual Studio build Search for "mysqld-debug" even in source tree
-
igor@olga.mysql.com authored
into olga.mysql.com:/home/igor/dev-opt/mysql-5.0-opt-bug30219
-
igor@olga.mysql.com authored
This bug manifested itself for queries with grouping by columns of the BIT type. It led to wrong comparisons of bit-field values and wrong result sets. Bit-field values never cannot be compared as binary values. Yet the class Field_bit had an implementation of the cmp method that compared bit-fields values as binary values. Also the get_image and set_image methods of the base class Field cannot be used for objects of the Field_bit class. Now these methods are declared as virtual and specific implementations of the methods are provided for the class Field_bit.
-
df@pippilotta.erinye.com authored
into pippilotta.erinye.com:/shared/home/df/mysql/build/mysql-5.0-build
-
df@pippilotta.erinye.com authored
into pippilotta.erinye.com:/shared/home/df/mysql/build/mysql-5.0-build
-
df@pippilotta.erinye.com authored
into pippilotta.erinye.com:/shared/home/df/mysql/build/mysql-4.1-build
-
gkodinov/kgeorge@magare.gmz authored
merged 5.1-main to 5.1-opt : error numbers changed. Many files: merged 5.1-main to 5.1-opt : error numbers changed rpl_extraCol_innodb.result: merged 5.1-main to 5.1-opt : error numbers changed
-
dlenev@mockturtle.local authored
when its statement being KILLed". The bug itself was fixed by separate patch in 5.0 tree.
-
dlenev@mockturtle.local authored
into mockturtle.local:/home/dlenev/src/mysql-5.1-bg21281-2
-
dlenev@mockturtle.local authored
statement being KILLed". When statement which was trying to obtain write lock on then table and which was blocked by existing read lock was killed, concurrent statements that were trying to obtain read locks on the same table and that were blocked by the presence of this pending write lock were not woken up and had to wait until this first read lock goes away. This problem was caused by the fact that we forgot to wake up threads which pending requests could have been satisfied after removing lock request for the killed thread. The patch solves the problem by waking up those threads in such situation. Test for this bug will be added to 5.1 only as it has much better facilities for its implementation. Particularly, by using I_S.PROCESSLIST and wait_condition.inc script we can wait until thread will be blocked on certain table lock without relying on unconditional sleep (which usage increases time needed for test runs and might cause spurious test failures on slower platforms).
-
igor@olga.mysql.com authored
into olga.mysql.com:/home/igor/dev-opt/mysql-5.1-opt-merge
-