- 28 Feb, 2008 1 commit
-
-
NAME_CONST('whatever', -1) * MAX(whatever) bombed since -1 was not seen as constant, but as FUNCTION_UNARY_MINUS(constant) while we are at the same time pretending it was a basic const item. This confused the aggregate handlers in exciting ways. We now make NAME_CONST() behave more consistently.
-
- 27 Feb, 2008 1 commit
-
-
holyfoot/hf@mysql.com/hfmain.(none) authored
There was no way to return an error from the client library if no MYSQL connections was established. So here i added variables to store that king of errors and made functions like mysql_error(NULL) to return these.
-
- 01 Feb, 2008 1 commit
-
-
kaa@mbp.local authored
on table creates The problem was in incompatible syntax for key definition in CREATE TABLE. 5.0 supports only the following syntax for key definition (see "CREATE TABLE syntax" in the manual): {INDEX|KEY} [index_name] [index_type] (index_col_name,...) While 5.1 parser supports the above syntax, the "preferred" syntax was changed to: {INDEX|KEY} [index_name] (index_col_name,...) [index_type] The above syntax is used in 5.1 for the SHOW CREATE TABLE output, which led to dumps generated by 5.1 being incompatible with 5.0. Fixed by changing the parser in 5.0 to support both 5.0 and 5.1 syntax for key definition.
-
- 20 Jan, 2008 1 commit
-
-
kaa@kaamos.(none) authored
of cleanups in the test case for bug33794.
-
- 18 Jan, 2008 2 commits
-
-
mhansson@lamia.dupka authored
into lamia.dupka:/home/mhansson/my50-bug33143-again-pushee
-
sergefp@mysql.com authored
The problem occurred when one had a subquery that had an equality X=Y where Y referred to a named select list expression from the parent select. MySQL crashed when trying to use the X=Y equality for ref-based access. Fixed by allowing non-Item_field items in the described case.
-
- 17 Jan, 2008 1 commit
-
-
mhansson/martin@linux-st28.site authored
into linux-st28.site:/home/martin/mysql/src/bug33143/my50-bug33143-again-pushee
-
- 14 Jan, 2008 1 commit
-
-
mhansson/martin@linux-st28.site authored
The ROUND(X, D) function would change the Item::decimals field during execution to achieve the effect of a dynamic number of decimal digits. This caused a series of bugs: Bug #30617:Round() function not working under some circumstances in InnoDB Bug #33402:ROUND with decimal and non-constant cannot round to 0 decimal places Bug #30889:filesort and order by with float/numeric crashes server Fixed by never changing the number of shown digits for DECIMAL when used with a nonconstant number of decimal digits.
-
- 12 Jan, 2008 1 commit
-
-
mhansson@lamia.dupka authored
into lamia.dupka:/home/mhansson/my50-bug31797-pushee
-
- 11 Jan, 2008 3 commits
-
-
mhansson/martin@linux-st28.site authored
into linux-st28.site:/home/martin/mysql/src/bug31797/my50-bug31797-pushee
-
mhansson/martin@linux-st28.site authored
The name resolution for correlated subqueries and HAVING clauses failed to distinguish which of two was being performed when there was a reference to an outer aliased field. Fixed by adding the condition that HAVING clause name resulotion is being performed.
-
evgen@moonbone.local authored
value when inserting into a view. The mysql_prepare_insert function checks all fields of the target table that directly or indirectly (through a view) are specified in the INSERT statement to have a default value. This check can be skipped if the INSERT statement doesn't mention any insert fields. In case of a view this allows fields that aren't mentioned in the view to bypass the check. Now fields of the target table are always checked to have a default value when insert goes into a view.
-
- 10 Jan, 2008 5 commits
-
-
kaa@kaamos.(none) authored
into kaamos.(none):/data/src/opt/mysql-5.0-opt
-
evgen@moonbone.local authored
into moonbone.local:/work/33675-bug-5.0-opt-mysql
-
evgen@moonbone.local authored
Bug#33675: Usage of an uninitialized memory by filesort in a subquery caused server crash. Free smaller buffer before allocating bigger one.
-
kaa@kaamos.(none) authored
into kaamos.(none):/data/src/opt/mysql-5.0-opt
-
kaa@kaamos.(none) authored
into kaamos.(none):/data/src/opt/mysql-5.0-opt
-
- 09 Jan, 2008 3 commits
-
-
evgen@moonbone.local authored
into moonbone.local:/work/33675-bug-5.0-opt-mysql
-
gkodinov/kgeorge@magare.gmz authored
into magare.gmz:/home/kgeorge/mysql/autopush/B33133-5.0-opt
-
gkodinov/kgeorge@macbook.gmz authored
When resolving references we need to take into consideration the view "fields" and allow qualified access to them. Fixed by extending the reference resolution to process view fields correctly.
-
- 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
-
- 24 Dec, 2007 1 commit
-
-
kaa@polly.(none) authored
to be compiled in The problem was that on a statically built server an attempt to create a UDF resulted in a different, but reasonable error ("Can't open shared library" instead of "UDFs are unavailable with the --skip-grant-tables option"), which caused a failure for the test case for bug #32020. Fixed by moving the test case for bug #32020 from skip_grants.test to a separate test to ensure that it is only run when the server is built with support for dynamically loaded libraries.
-
- 21 Dec, 2007 3 commits
-
-
joerg@trift2. authored
into trift2.:/MySQL/M50/merge-5.0
-
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.
-
df@pippilotta.erinye.com authored
into pippilotta.erinye.com:/shared/home/df/mysql/build/mysql-5.0-build
-
- 20 Dec, 2007 5 commits
-
-
df@pippilotta.erinye.com authored
-
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 7 commits
-
-
df@pippilotta.erinye.com authored
into pippilotta.erinye.com:/shared/home/df/mysql/build/mysql-5.0-build
-
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_
-
into mysql.com:/misc/mysql/31752_/41-31752_
-
joerg@trift2. authored
into trift2.:/MySQL/M50/push-5.0
-
tnurnberg@white.intern.koehntopp.de authored
into mysql.com:/misc/mysql/31752_/50-31752_
-