1. 16 May, 2006 1 commit
  2. 15 May, 2006 4 commits
  3. 12 May, 2006 14 commits
  4. 11 May, 2006 2 commits
  5. 10 May, 2006 14 commits
  6. 09 May, 2006 5 commits
    • acurtis@xiphis.org's avatar
      Merge xiphis.org:/home/antony/work2/p1-bug10952.1 · 22b6b4cb
      acurtis@xiphis.org authored
      into  xiphis.org:/home/antony/work2/mysql-5.0-engines-merge
      22b6b4cb
    • acurtis@xiphis.org's avatar
      Merge acurtis@bk-internal:/home/bk/mysql-5.0-engines · 7c9b4c27
      acurtis@xiphis.org authored
      into  xiphis.org:/home/antony/work2/p1-bug10952.1
      7c9b4c27
    • acurtis@xiphis.org's avatar
      bug#10952 · 47e89f20
      acurtis@xiphis.org authored
        "alter table from MyISAM to MERGE lost data without errors and warnings"
        Add new handlerton flag which prevent user from altering table storage
        engine to storage engines which would lose data. Both 'blackhole' and 
        'merge' are marked with the new flag.
        Tests included.
      47e89f20
    • gkodinov@mysql.com's avatar
      BUG#18068: SELECT DISTINCT (with duplicates and covering index) · 7bae0de3
      gkodinov@mysql.com authored
      When converting DISTINCT to GROUP BY where the columns are from the covering
      index and they are quoted twice in the SELECT list the optimizer is creating
      improper processing sequence. This is because of the fact that the columns
      of the covering index are not recognized as such and treated as non-index
      columns.
      
      Generally speaking duplicate columns can safely be removed from the GROUP
      BY/DISTINCT list because this will not add or remove new rows in the
      resulting set. Duplicates can be removed even if they are not consecutive
      (as is the case for ORDER BY, where the duplicate columns can be removed
      only if they are consecutive).
      
      So we can safely transform "SELECT DISTINCT a,a FROM ... ORDER BY a" to
      "SELECT a,a FROM ... GROUP BY a ORDER BY a" instead of 
      "SELECT a,a FROM .. GROUP BY a,a ORDER BY a". We can even transform 
      "SELECT DISTINCT a,b,a FROM ... ORDER BY a,b" to
      "SELECT a,b,a FROM ... GROUP BY a,b ORDER BY a,b".
      
      The fix to this bug consists of checking for duplicate columns in the SELECT
      list when constructing the GROUP BY list in transforming DISTINCT to GROUP
      BY and skipping the ones that are already in.
      7bae0de3
    • msvensson@neptunus.(none)'s avatar
      Merge neptunus.(none):/home/msvensson/mysql/mysql-5.0 · 98cc7412
      msvensson@neptunus.(none) authored
      into  neptunus.(none):/home/msvensson/mysql/mysql-5.0-maint
      98cc7412