An error occurred fetching the project authors.
  1. 16 Oct, 2006 1 commit
    • gkodinov/kgeorge@macbook.gmz's avatar
      Bug #22342: No results returned for query using max and group by · 0e954d2c
      gkodinov/kgeorge@macbook.gmz authored
       When using index for group by and range access the server isolates    
       a set of ranges based on the conditions over the key parts of the
       index used. Then it uses only the ranges over the GROUP BY fields to
       jump from one group to another. Since the GROUP BY fields may form a
       prefix over the index, we may use only a prefix of the ranges produced
       by the range optimizer.
       Each range contains a notion on whether it includes its border values.
       The problem is that when using a range prefix, the last range is open
       because it assumes that there is a range on the next keypart. Thus when
       we use a prefix range as it is, it excludes all border values.
       The solution is when ignoring the suffix of the range conditions 
       (to jump over the GROUP BY prefix only) the server must change the 
       remaining intervals so they always contain their borders, e.g. 
       if the whole range was :
       (1,-inf) <= (<group_by_col>,<min_max_arg_col>) < (1, 3) we must make
       (1) <= (<group_by_col>) <= (1) because (a,b) < (c1,c2) means :
       a < c1 OR (a = c1 AND b < c2).
      0e954d2c
  2. 18 Sep, 2006 1 commit
  3. 15 Aug, 2006 1 commit
    • sergefp@mysql.com's avatar
      BUG#21077: Possible crash caused by invalid sequence of handler::* calls: ... · 86c5cad4
      sergefp@mysql.com authored
      BUG#21077: Possible crash caused by invalid sequence of handler::* calls:                                                
      The crash was caused by invalid sequence of handler::** calls:                                                           
        ha_smth->index_init();                                                                                                 
        ha_smth->index_next_same(); (2)                                                                                        
      (2) is an invalid call as it was not preceeded by any 'scan setup' call
      like index_first() or index_read(). The cause was that QUICK_SELECT::reset()
      didn't "fully reset" the quick select- current QUICK_RANGE wasn't forgotten,
      and quick select might attempt to continue reading the range, which would
      result in the above mentioned invalid sequence of handler calls.
      
      5.x versions are not affected by the bug - they already have the missing
      "range=NULL" clause.                                                    
                                                             
      86c5cad4
  4. 03 Aug, 2006 1 commit
  5. 15 Jul, 2006 1 commit
    • igor@rurik.mysql.com's avatar
      Fixed bug #20869. · 38cd55a7
      igor@rurik.mysql.com authored
      The bug caused a crash of the server if a subquery with
      ORDER BY DESC used the range access method.
      The bug happened because the method QUICK_SELECT_DESC::reset
      was not reworked after MRR interface had been introduced.
      38cd55a7
  6. 03 Jan, 2006 1 commit
  7. 30 Sep, 2005 1 commit
  8. 03 Jun, 2005 1 commit
    • monty@mysql.com's avatar
      Move USE_PRAGMA_IMPLEMENTATION to proper place · 29fd1f2f
      monty@mysql.com authored
      Ensure that 'null_value' is not accessed before val() is called in FIELD() functions
      Fixed initialization of key maps. This fixes some problems with keys when you have more than 64 keys
      Fixed that ROLLUP don't always create a temporary table. This fix ensures that func_gconcat.test results are now predictable
      29fd1f2f
  9. 02 Jun, 2005 1 commit
  10. 04 May, 2005 1 commit
  11. 28 Apr, 2005 1 commit
    • sergefp@mysql.com's avatar
      Fix for BUG#10244: · a7a1d4dc
      sergefp@mysql.com authored
      Make get_quick_select_for_ref() accept estimated # records as parameter and 
      set QUICK_RANGE_SELECT::records, as this value is used to allocate buffers 
      in Multi-Range Read. 
      a7a1d4dc
  12. 29 Dec, 2004 1 commit
    • sergefp@mysql.com's avatar
      Post WL#2126 fixes: · fb0845f8
      sergefp@mysql.com authored
       * remove get_next_init and move its functionality to QUICK_RANGE_SELECT::reset()
       * added more comments
       * added empty FT_SELECT::reset() 
      fb0845f8
  13. 23 Dec, 2004 1 commit
  14. 21 Nov, 2004 1 commit
    • sergefp@mysql.com's avatar
      Fix for BUG#4177: · e6a7386c
      sergefp@mysql.com authored
       * Make index merge quick selects code allow perform several scans.
       * Delay additional handler objects creation till row retrieval is started.
      e6a7386c
  15. 16 Nov, 2004 1 commit
  16. 27 Aug, 2004 1 commit
  17. 11 Aug, 2004 1 commit
  18. 21 Jul, 2004 1 commit
  19. 20 Jul, 2004 1 commit
  20. 15 Jul, 2004 2 commits
  21. 23 Jun, 2004 1 commit
    • serg@serg.mylan's avatar
      handler interface cleanups: · 3f1c4ba7
      serg@serg.mylan authored
        more logical table/index_flags
        return  HA_ERR_WRONG_COMMAND instead of abstract methods where appropriate
        max_keys and other limits renamed to max_supported_keys/etc
        max_keys/etc are now wrappers to max_supported_keys/etc 
        ha_index_init/ha_rnd_init/ha_index_end/ha_rnd_end are now wrappers to real {index,rnd}_{init,end} to enforce strict pairing
      3f1c4ba7
  22. 01 Jun, 2004 1 commit
  23. 28 May, 2004 1 commit
    • sergefp@mysql.com's avatar
      * New index_merge EXPLAIN output format · dff98a8e
      sergefp@mysql.com authored
       * Fixed a problem with wrong query results for partially covering keys in ROR-index_merge
       * ROR-intersection retrieval plan choice algorithm now uses less disk IO
         - and properly processes clustered PK range scans 
       * Fixed several minor range optimizer problems
       * Added more comments
       * Code cleanup
      dff98a8e
  24. 16 May, 2004 1 commit
    • monty@mishka.local's avatar
      key_cmp -> key_cmp_if_same · 314a8bf1
      monty@mishka.local authored
      New records_in_range() interface (similar to read_range())
      Macros for faster bitmap handling
      Simplify read_range() code (#WL1786)
      New general key_cmp() function to compare keys
      
      314a8bf1
  25. 14 May, 2004 1 commit
    • pem@mysql.comhem.se's avatar
      Post-merge fixes. · ec921065
      pem@mysql.comhem.se authored
      Note: One sp.test still fails (prime), and rpl_server_id2.test fails (will be fixed by guilhem ASAP).
      ec921065
  26. 12 May, 2004 1 commit
  27. 08 Apr, 2004 1 commit
  28. 07 Apr, 2004 1 commit
  29. 15 Mar, 2004 1 commit
  30. 11 Feb, 2004 1 commit
  31. 05 Feb, 2004 1 commit
  32. 03 Feb, 2004 1 commit
  33. 02 Feb, 2004 1 commit
  34. 18 Dec, 2003 1 commit
  35. 09 Dec, 2003 1 commit
  36. 24 Nov, 2003 1 commit
  37. 21 Nov, 2003 1 commit
  38. 20 Nov, 2003 1 commit
    • sergefp@mysql.com's avatar
      logging_ok: · 4016048d
      sergefp@mysql.com authored
        Logging to logging@openlogging.org accepted
      sql_union.cc, sql_select.cc, opt_range.h, opt_range.cc, opt_ft.h:
        Post-merge fixes
      Many files:
        new file
      4016048d
  39. 18 Nov, 2003 1 commit