- 19 Jan, 2008 1 commit
-
-
kaa@kaamos.(none) authored
into kaamos.(none):/data/src/opt/mysql-5.1-opt
-
- 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 3 commits
-
-
mhansson/martin@linux-st28.site authored
into linux-st28.site:/home/martin/mysql/src/bug33143/my51-bug33143-pushee
-
mhansson/martin@linux-st28.site authored
into linux-st28.site:/home/martin/mysql/src/bug33143/my51-bug33143
-
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 10 commits
-
-
mhansson@lamia.dupka authored
into lamia.dupka:/home/mhansson/my51-bug31797-pushee
-
mhansson/martin@linux-st28.site authored
into linux-st28.site:/home/martin/mysql/src/bug31797/my51-bug31797-pushee
-
mhansson/martin@linux-st28.site authored
into linux-st28.site:/home/martin/mysql/src/bug31797/my51-bug31797
-
igor@olga.mysql.com authored
into olga.mysql.com:/home/igor/dev-opt/mysql-5.1-opt-bug33697
-
igor@olga.mysql.com authored
When the function test_if_skip_sort_order prefers index backward scan to ref access the corresponding access functions must be set accordingly.
-
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.
-
gshchepa/uchum@host.loc authored
into host.loc:/home/uchum/work/5.1-opt
-
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.
-
gshchepa/uchum@host.loc authored
columns (default datatype value is assigned). The mysql_update function has been modified to generate an error when trying to set a NOT NULL field to NULL rather than a warning in the set_field_to_null_with_conversions function.
-
- 10 Jan, 2008 12 commits
-
-
kaa@kaamos.(none) authored
into kaamos.(none):/data/src/opt/mysql-5.1-opt
-
kaa@kaamos.(none) authored
into kaamos.(none):/data/src/opt/mysql-5.1-opt
-
kaa@kaamos.(none) authored
into kaamos.(none):/data/src/opt/mysql-5.0-opt
-
epotemkin@bk-internal.mysql.com authored
into bk-internal.mysql.com:/data0/bk/mysql-5.1-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
-
kaa@kaamos.(none) authored
into kaamos.(none):/data/src/opt/mysql-5.1-opt
-
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.1-opt
-
kaa@kaamos.(none) authored
into kaamos.(none):/data/src/opt/mysql-5.0-opt
-
kaa@kaamos.(none) authored
into kaamos.(none):/data/src/opt/bug33305/my51-bug33305
-
- 09 Jan, 2008 5 commits
-
-
evgen@moonbone.local authored
into moonbone.local:/work/33675-bug-5.0-opt-mysql
-
gkodinov/kgeorge@macbook.gmz authored
-
gkodinov/kgeorge@macbook.gmz authored
into macbook.gmz:/Users/kgeorge/mysql/work/B33133-5.1-opt
-
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 3 commits
-
-
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.
-
gkodinov/kgeorge@macbook.gmz authored
-
gkodinov/kgeorge@macbook.gmz authored
into macbook.gmz:/Users/kgeorge/mysql/work/B33256-5.1-opt
-
- 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.
-