1. 28 Feb, 2008 1 commit
  2. 27 Feb, 2008 1 commit
  3. 01 Feb, 2008 1 commit
    • kaa@mbp.local's avatar
      Fix for bug #25162: Backing up DB from 5.1 adds 'USING BTREE' to KEYs · 663453d5
      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.
      663453d5
  4. 20 Jan, 2008 1 commit
  5. 18 Jan, 2008 2 commits
  6. 17 Jan, 2008 1 commit
  7. 14 Jan, 2008 1 commit
    • mhansson/martin@linux-st28.site's avatar
      Bug#33143: Incorrect ORDER BY for ROUND()/TRUNCATE() result · effe27e3
      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.
      effe27e3
  8. 12 Jan, 2008 1 commit
  9. 11 Jan, 2008 3 commits
  10. 10 Jan, 2008 5 commits
  11. 09 Jan, 2008 3 commits
  12. 08 Jan, 2008 1 commit
    • evgen@moonbone.local's avatar
      Bug#33675: Usage of an uninitialized memory by filesort in a subquery caused · ce111a0d
      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.
      ce111a0d
  13. 07 Jan, 2008 1 commit
  14. 24 Dec, 2007 1 commit
    • kaa@polly.(none)'s avatar
      Fix for bug #33305: Test case in 'skip_grants' file need dynamic loading · 578b3632
      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.
      578b3632
  15. 21 Dec, 2007 3 commits
  16. 20 Dec, 2007 5 commits
  17. 19 Dec, 2007 1 commit
  18. 18 Dec, 2007 1 commit
  19. 17 Dec, 2007 7 commits