- 08 Jan, 2008 1 commit
-
-
evgen@moonbone.local authored
server crash. The filesort implementation has an optimization for subquery execution which consists of reusing previously allocated buffers. In particular the call to the read_buffpek_from_file function might be skipped when a big enough buffer for buffer descriptors (buffpeks) is already allocated. Beside allocating memory for buffpeks this function fills allocated buffer with data read from disk. Skipping it might led to using an arbitrary memory as fields' data and finally to a crash. Now the read_buffpek_from_file function is always called. It allocates new buffer only when necessary, but always fill it with correct data.
-
- 07 Jan, 2008 1 commit
-
-
gkodinov/kgeorge@magare.gmz authored
into magare.gmz:/home/kgeorge/mysql/autopush/B33256-5.0-opt
-
- 21 Dec, 2007 1 commit
-
-
gkodinov/kgeorge@macbook.gmz authored
w/ Field_date instead of Field_newdate Field_date was still used in temp table creation. Fixed by using Field_newdate consistently throughout the server except when reading tables defined with older MySQL version. No test suite is possible because both Field_date and Field_newdate return the same values in all the metadata calls.
-
- 20 Dec, 2007 4 commits
-
-
tnurnberg@white.intern.koehntopp.de authored
into mysql.com:/misc/mysql/31990/50-31990
-
mhansson/martin@linux-st28.site authored
into linux-st28.site:/home/martin/mysql/src/bug32848/my50-bug32848
-
mhansson/martin@linux-st28.site authored
Warnings elimination
-
tnurnberg@white.intern.koehntopp.de authored
into mysql.com:/misc/mysql/31990/50-31990
-
- 19 Dec, 2007 1 commit
-
-
mhansson/martin@linux-st28.site authored
into linux-st28.site:/home/martin/mysql/src/bug32848/my50-bug32848
-
- 18 Dec, 2007 1 commit
-
-
gkodinov/kgeorge@magare.gmz authored
into magare.gmz:/home/kgeorge/mysql/autopush/B19390-5.0-opt
-
- 17 Dec, 2007 9 commits
-
-
gkodinov/kgeorge@magare.gmz authored
The checks in the test for bug #12480 were too wide and made the test to depend on the procedures and triggers present in the server. Corrected the test to check only for the procedure and trigger it creates.
-
tnurnberg@white.intern.koehntopp.de authored
into mysql.com:/misc/mysql/32770/50-32770
-
tnurnberg@white.intern.koehntopp.de authored
into mysql.com:/misc/mysql/31752_/50-31752_
-
tnurnberg@white.intern.koehntopp.de authored
into mysql.com:/misc/mysql/31752_/50-31752_
-
fix test program
-
tnurnberg@white.intern.koehntopp.de authored
into mysql.com:/misc/mysql/32770/50-32770
-
tnurnberg@white.intern.koehntopp.de authored
into mysql.com:/misc/mysql/31752_/50-31752_
-
into mysql.com:/misc/mysql/31752_/50-31752_
-
tnurnberg@white.intern.koehntopp.de authored
into mysql.com:/misc/mysql/32770/50-32770
-
- 15 Dec, 2007 4 commits
-
-
mhansson/martin@linux-st28.site authored
into linux-st28.site:/home/martin/mysql/src/bug32798-united/my50-bug32798-united-push
-
mhansson/martin@linux-st28.site authored
into linux-st28.site:/home/martin/mysql/src/bug32858/my50-bug32858-push
-
mhansson/martin@linux-st28.site authored
into linux-st28.site:/home/martin/mysql/src/bug32798-united/my50-bug32798-united-push
-
igor@olga.mysql.com authored
into olga.mysql.com:/home/igor/dev-opt/mysql-5.0-opt-bug27848
-
- 14 Dec, 2007 2 commits
-
-
igor@olga.mysql.com authored
In a union without braces, the order by at the end is applied to the overall union. It therefore should not interfere with the individual select parts of the union. Fixed by changing our parser rules appropriately.
-
mhansson/martin@linux-st28.site authored
with null values For queries containing GROUP_CONCAT(DISTINCT fields ORDER BY fields), there was a limitation that the DISTINCT fields had to be the same as ORDER BY fields, owing to the fact that one single sorted tree was used for keeping track of tuples, ordering and uniqueness. Fixed by introducing a second structure to handle uniqueness so that the original structure has only to order the result.
-
- 13 Dec, 2007 9 commits
-
-
gluh@mysql.com/eagle.(none) authored
-
gluh@mysql.com/eagle.(none) authored
-
gluh@mysql.com/eagle.(none) authored
-
gluh@eagle.(none) authored
into mysql.com:/home/gluh/MySQL/Merge/5.0-opt
-
gluh@eagle.(none) authored
into mysql.com:/home/gluh/MySQL/Merge/5.0-opt
-
sergefp@foxhole.(none) authored
into mysql.com:/home/psergey/mysql-5.0-bug32198
-
sergefp@mysql.com authored
- Make conditions like "date_col $CMP$ 'datetime-const'" range-sargable
-
gluh@mysql.com/eagle.(none) authored
into mysql.com:/home/gluh/MySQL/Merge/4.1-opt
-
mhansson/martin@linux-st28.site authored
subselects into account It is forbidden to use the SELECT INTO construction inside UNION statements unless on the last SELECT of the union. The parser records whether it has seen INTO or not when parsing a UNION statement. But if the INTO was legally used in an outer query, an error is thrown if UNION is seen in a subquery. Fixed in 5.0 by remembering the nesting level of INTO tokens and mitigate the error unless it collides with the UNION.
-
- 12 Dec, 2007 1 commit
-
-
istruewing@stella.local authored
Fixed case of comment.
-
- 11 Dec, 2007 5 commits
-
-
istruewing@stella.local authored
into stella.local:/home2/mydev/mysql-5.0-axmrg
-
mhansson/martin@linux-st28.site authored
There were two problems when inferring the correct field types resulting from UNION queries. - If the type is NULL for all corresponding fields in the UNION, the resulting type would be NULL, while the type is BINARY(0) if there is just a single SELECT NULL. - If one SELECT in the UNION uses a subselect, a temporary table is created to represent the subselect, and the result type defaults to a STRING type, hiding the fact that the type was unknown(just a NULL value). Fixed by remembering whenever a field was created from a NULL value and pass type NULL to the type coercion if that is the case, and creating a string field as result of UNION only if the type would otherwise be NULL.
-
df@pippilotta.erinye.com authored
-
istruewing@stella.local authored
into stella.local:/home2/mydev/mysql-5.0-axmrg
-
HOUR(), MINUTE(), ... returned spurious results when used on a DATE-cast. This happened because DATE-cast object did not overload get_time() method in superclass Item. The default method was inappropriate here and misinterpreted the data. Patch adds missing method; get_time() on DATE-casts now returns SQL-NULL on NULL input, 0 otherwise. This coincides with the way DATE-columns behave. Also fixes similar bug in Date-Field now.
-
- 10 Dec, 2007 1 commit
-
-
df@pippilotta.erinye.com authored
into pippilotta.erinye.com:/shared/home/df/mysql/build/mysql-5.0-build
-