An error occurred fetching the project authors.
- 14 Jun, 2007 10 commits
-
-
holyfoot/hf@hfmain.(none) authored
into mysql.com:/d2/hf/mrg/mysql-5.1-opt
-
gkodinov/kgeorge@magare.gmz authored
into magare.gmz:/home/kgeorge/mysql/work/valgrind-errs-5.1-opt
-
gkodinov/kgeorge@magare.gmz authored
into magare.gmz:/home/kgeorge/mysql/work/valgrind-errs-merge-5.0-opt
-
gkodinov/kgeorge@magare.gmz authored
-
holyfoot/hf@hfmain.(none) authored
into mysql.com:/d2/hf/mrg/mysql-5.1-opt
-
holyfoot/hf@hfmain.(none) authored
into mysql.com:/d2/hf/mrg/mysql-5.1-opt
-
holyfoot/hf@hfmain.(none) authored
into mysql.com:/d2/hf/mrg/mysql-5.0-opt
-
holyfoot/hf@hfmain.(none) authored
into mysql.com:/d2/hf/mrg/mysql-5.1-opt
-
gkodinov/kgeorge@magare.gmz authored
into magare.gmz:/home/kgeorge/mysql/autopush/B28991-5.1-opt
-
gkodinov/kgeorge@magare.gmz authored
In tests waiting on a timeout is not deterministic enough to make sure that an event actually finished executing. Fixed the test by waiting in a loop and checking the effect that the event is supposed to produce.
-
- 13 Jun, 2007 2 commits
-
-
igor@olga.mysql.com authored
was erroneously converted to double, while the result of ROUND(<decimal expr>, <int literal>) was preserved as decimal. As a result of such a conversion the value of ROUND(D,A) could differ from the value of ROUND(D,val(A)) if D was a decimal expression. Now the result of the ROUND function is never converted to double if the first argument is decimal.
-
mhansson@dl145s.mysql.com authored
into dl145s.mysql.com:/users/mhansson/mysql/autopush/5.1o-bug27634
-
- 12 Jun, 2007 12 commits
-
-
gkodinov/kgeorge@magare.gmz authored
into magare.gmz:/home/kgeorge/mysql/autopush/B27816-5.1-opt
-
gkodinov/kgeorge@magare.gmz authored
into magare.gmz:/home/kgeorge/mysql/work/merge-5.1-opt
-
gkodinov/kgeorge@magare.gmz authored
-
gkodinov/kgeorge@magare.gmz authored
into magare.gmz:/home/kgeorge/mysql/work/merge-5.1-opt
-
holyfoot/hf@hfmain.(none) authored
into mysql.com:/home/hf/work/28757/my51-28757
-
holyfoot/hf@mysql.com/hfmain.(none) authored
the reported test failure is fixed by the patch to 28333, but there's a bit more to fix in the test itself - to drop tables created in this test at the test's beginning.
-
mhansson/martin@linux-st28.site authored
On many architectures, e.g. 68000, x86, the double registers have higher precision than the IEEE standard prescribes. When compiled with flags -O and higher, some double's go into registers and therefore have higher precision. In one test case the cost information of the best and second-best key were close enough to be influenced by this effect, causing a failed test in distribution builds. Fixed by removing some rows from the table in question so that cost information is not influenced by decimals beyond standard definition of double.
-
gkodinov/kgeorge@magare.gmz authored
-
gkodinov/kgeorge@magare.gmz authored
into magare.gmz:/home/kgeorge/mysql/autopush/B28992-5.0-opt
-
gkodinov/kgeorge@magare.gmz authored
- fixed wrong test case for bug 20903 - closed the dangling connections in trigger.test - GET_LOCK() and RELEASE_LOCK() now produce more detailed log - fixed an omission in GET_LOCK() : assign the thread_id when acquiring the lock.
-
gkodinov/kgeorge@magare.gmz authored
into magare.gmz:/home/kgeorge/mysql/autopush/B28934-5.0-opt
-
gkodinov/kgeorge@magare.gmz authored
Sometimes a parameter slot may not get a value because of the protocol data being plain wrong. Such cases should be detected and handled by returning an error. Fixed by checking data stream constraints where possible (like maximum length) and reacting to the case where a value cannot be constructed.
-
- 11 Jun, 2007 6 commits
-
-
evgen@moonbone.local authored
When the INSERT .. ON DUPLICATE KEY UPDATE has to update a matched row but the new data is the same as in the record then it returns as if no rows were inserted or updated. Nevertheless the row is silently updated. This leads to a situation when zero updated rows are reported in the case when data has actually been changed. Now the write_record function updates a row only if new data differs from that in the record.
-
evgen@moonbone.local authored
Post merge fix.
-
evgen@moonbone.local authored
into moonbone.local:/mnt/gentoo64/work/test-5.1-opt-mysql
-
evgen@moonbone.local authored
Post merge fix.
-
evgen@moonbone.local authored
into moonbone.local:/mnt/gentoo64/work/test-5.1-opt-mysql
-
evgen@moonbone.local authored
Post merge fix.
-
- 10 Jun, 2007 1 commit
-
-
evgen@moonbone.local authored
into moonbone.local:/mnt/gentoo64/work/test-5.1-opt-mysql
-
- 09 Jun, 2007 9 commits
-
-
gluh@mysql.com/eagle.(none) authored
-
gluh@eagle.(none) authored
into mysql.com:/home/gluh/MySQL/Merge/5.0-opt
-
gluh@mysql.com/eagle.(none) authored
changed bytes_received, bytes_sent status variables to longlong
-
holyfoot/hf@hfmain.(none) authored
into mysql.com:/home/hf/work/28333/my50-28333
-
gluh@mysql.com/eagle.(none) authored
IS_UPDATABLE flag is set to 'yes' when the view has at least one updatable column and the algorithm is not 'temporary'.
-
holyfoot/hf@hfmain.(none) authored
into mysql.com:/home/hf/work/28333/my51-28333
-
gluh@mysql.com/eagle.(none) authored
-
holyfoot/hf@hfmain.(none) authored
into mysql.com:/home/hf/work/28333/my50-28333
-
holyfoot/hf@hfmain.(none) authored
into mysql.com:/home/hf/work/28333/my51-28333
-