- 24 Feb, 2009 2 commits
-
-
Daniel Fischer authored
-
Daniel Fischer authored
transparent what kinds of tests we run during integration testing.
-
- 07 Feb, 2009 3 commits
-
-
Timothy Smith authored
-
Joerg Bruehe authored
-
- 06 Feb, 2009 9 commits
-
-
Joerg Bruehe authored
-
Joerg Bruehe authored
This involves just the tag, no file changes - they were all present before.
-
Timothy Smith authored
-
Tatiana A. Nurnberg authored
-
Tatiana A. Nurnberg authored
In 37553 we declared longlong results for class Item_str_timefunc as per comments/docs, but didn't add a method for that. And the default just wasn't good enough for some cases. Changeset adds dedicated val_int() to class.
-
Timothy Smith authored
-
Timothy Smith authored
-
Georgi Kodinov authored
-
Alexey Kopytov authored
-
- 05 Feb, 2009 4 commits
-
-
Alexey Kopytov authored
-
Alexey Kopytov authored
-
Gleb Shchepa authored
ORDER BY could cause a server crash Dependent subqueries like SELECT COUNT(*) FROM t1, t2 WHERE t2.b IN (SELECT DISTINCT t2.b FROM t2 WHERE t2.b = t1.a) caused a memory leak proportional to the number of outer rows. The make_simple_join() function has been modified to JOIN class method to store join_tab_reexec and table_reexec values in the parent join only (make_simple_join of tmp_join may access these values via 'this' pointer of the parent JOIN). NOTE: this patch doesn't include standard test case (this is "out of memory" bug). See bug #42037 page for test cases.
-
Ramil Kalimullin authored
Problem: some queries using NAME_CONST(.. COLLATE ...) lead to server crash due to failed type cast. Fix: return the underlying item's type in case of NAME_CONST(.. COLLATE ...) to avoid wrong casting.
-
- 04 Feb, 2009 4 commits
-
-
Chad MILLER authored
-
Matthias Leich authored
-
Sergey Vojtovich authored
Accessing well defined MERGE table may return an error stating that the merge table is incorrectly defined. This happens if MERGE child tables were accessed before and we failed to open another incorrectly defined MERGE table in this connection. myrg_open() internally used my_errno as a variable for determining failure, and thus could be tricked into a wrong decision by other uses of my_errno. With this fix we use function local boolean flag instead of my_errno to determine failure.
-
Timothy Smith authored
simpler to just use the source .tar.gz to do a build. So the script has been renamed to nwbuild, and simplified.
-
- 03 Feb, 2009 2 commits
-
-
Alexey Kopytov authored
functions String::realloc() did not check whether the existing string data fits in the newly allocated buffer for cases when reallocating a String object with external buffer (i.e.alloced == FALSE). This could lead to memory overruns in some cases.
-
Georgi Kodinov authored
-
- 02 Feb, 2009 2 commits
-
-
Patrick Crews authored
The original symptoms of this bug have been fixed as a consequence of other bug fixes. Taking this time to correct some formatting, such as replacing error numbers with names. Beginning this with 5.0
-
Matthias Leich authored
- If missing: add "disconnect <session>" - If physical disconnect of non "default" sessions is not finished at test end: add routine which waits till this happened + additional improvements like - remove superfluous files created by the test - replace error numbers by error names - remove trailing spaces, replace tabs by spaces - unify writing of bugs within comments - correct comments - minor changes of formatting Modifications according to the code review are included. Fixed tests: grant2 grant3 lock_tables_lost_commit mysqldump openssl_1 outfile
-
- 31 Jan, 2009 1 commit
-
-
Tatiana A. Nurnberg authored
-
- 30 Jan, 2009 2 commits
-
-
Tatiana A. Nurnberg authored
When storing a NULL to a TIMESTAMP NOT NULL DEFAULT ..., NULL returned from some functions threw a 'cannot be NULL error.' NULL-returns now correctly result in the timestamp-field being assigned its default value.
-
Georgi Kodinov authored
-
- 29 Jan, 2009 3 commits
-
-
Joerg Bruehe authored
-
Georgi Kodinov authored
-
Georgi Kodinov authored
If the system time is adjusted back during a query execution (resulting in the end time being earlier than the start time) the code that prints to the slow query log gets confused and prints unsigned negative numbers. Fixed by not logging the statements that would have negative execution time due to time shifts. No test case since this would involve changing the system time.
-
- 28 Jan, 2009 5 commits
-
-
Gleb Shchepa authored
messed up "ROW(...) IN (SELECT ... FROM DUAL)" always returned TRUE. Item_in_subselect::row_value_transformer rewrites "ROW(...) IN SELECT" conditions into the "EXISTS (SELECT ... HAVING ...)" form. For a subquery from the DUAL pseudotable resulting HAVING condition is an expression on constant values, so further transformation with optimize_cond() eliminates this HAVING condition and resets JOIN::having to NULL. Then JOIN::exec treated that NULL as an always-true-HAVING and that caused a bug. To distinguish an optimized out "HAVING TRUE" clause from "HAVING FALSE" we already have the JOIN::having_value flag. However, JOIN::exec() ignored JOIN::having_value as described above as if it always set to COND_TRUE. The JOIN::exec method has been modified to take into account the value of the JOIN::having_value field.
-
Davi Arnaut authored
Dirty close tricky does not work on Windows.
-
Georgi Kodinov authored
Re-generated the PKI files needed. Removed the ones that are not needed. Updated the tests to reference the correct SSL subject.
-
Bjorn Munch authored
-
Bjorn Munch authored
Check for existence of diff fails on Solaris due to unsupported "-v" Fix is to do this check only on Windows where it was needed
-
- 26 Jan, 2009 2 commits
-
-
Joerg Bruehe authored
into the 5.0.72sp1 branch. Original changeset (in the main 5.0 branch): > committer: Kent Boortz <kent@kent-amd64> > branch nick: mysql-5.0-build-bug42278 > timestamp: Fri 2009-01-23 02:59:03 +0100
-
Chad MILLER authored
-
- 23 Jan, 2009 1 commit
-
-
Kent Boortz authored
packages, this is now corrected (Bug#42278)
-