An error occurred fetching the project authors.
  1. 02 Dec, 2005 1 commit
    • ingo@mysql.com's avatar
      Bug#10932 - Building server with key limit of 128, makes test cases fail · 6b18dbef
      ingo@mysql.com authored
      Allow for configuration of the maximum number of indexes per table.
      Added and used a configure.in macro.
      Replaced fixed limits by the configurable limit.
      Limited MyISAM indexes to its hard limit.
      Fixed a bug in opt_range.cc for many indexes with InnoDB.
      
      Tested for 2, 63, 64, 65, 127, 128, 129, 255, 256, and 257 indexes.
      Testing this part of the bugfix requires rebuilding of the server 
      with different options. This cannot be done with our test suite. 
      Therefore I added the necessary test files to the bug report.
      If you repeat the tests, please note that the ps_* tests fail for
      everything but 64 indexes. This is because of differences in the 
      meta data, namely field lengths for index names etc.
      6b18dbef
  2. 18 Nov, 2005 1 commit
  3. 17 Nov, 2005 1 commit
  4. 09 Nov, 2005 1 commit
  5. 03 Nov, 2005 1 commit
  6. 25 Oct, 2005 1 commit
  7. 13 Oct, 2005 2 commits
  8. 21 Sep, 2005 1 commit
    • konstantin@mysql.com's avatar
      A fix and a test case for Bug#6513 "Test Suite: Values inserted by using · 6f8d3c48
      konstantin@mysql.com authored
      cursor is interpreted latin1 character and Bug#9819 "Cursors: Mysql Server
      Crash while fetching from table with 5 million records."
      A fix for a possible memory leak when fetching into an SP cursor
      in a long loop.
      The patch uses a common implementation of cursors in the binary protocol and 
      in stored procedures and implements materialized cursors.
      For implementation details, see comments in sql_cursor.cc
      6f8d3c48
  9. 09 Sep, 2005 1 commit
    • gluh@eagle.intranet.mysql.r18.ru's avatar
      Bug#12817 SHOW STATUS now blob fields · 99bc9607
      gluh@eagle.intranet.mysql.r18.ru authored
         This fix is cancellation of ChangeSet
         1.2329 05/07/12 08:35:30 reggie@linux.site +8 -0
         Bug 7142  Show Fields from fails using Borland's dbExpress interface
         The reason is we can't fix bug#7142 without
         breaking of existing applications/APIs that worked fine with earlier 4.1
         bug 7142 is fixed in 5.0
      
      99bc9607
  10. 30 Aug, 2005 1 commit
  11. 26 Aug, 2005 1 commit
  12. 23 Aug, 2005 1 commit
    • timour@mysql.com's avatar
      WL#2486 - natural and using join according to SQL:2003 · e0403003
      timour@mysql.com authored
      * Provide backwards compatibility extension to name resolution of
        coalesced columns. The patch allows such columns to be qualified
        with a table (and db) name, as it is in 4.1.
        Based on a patch from Monty.
      
      * Adjusted tests accordingly to test both backwards compatible name
        resolution of qualified columns, and ANSI-style resolution of
        non-qualified columns.
        For this, each affected test has two versions - one with qualified
        columns, and one without. 
      e0403003
  13. 17 Aug, 2005 1 commit
  14. 12 Aug, 2005 1 commit
    • timour@mysql.com's avatar
      Implementation of WL#2486 - · a247282a
      timour@mysql.com authored
      "Process NATURAL and USING joins according to SQL:2003".
      
      * Some of the main problems fixed by the patch:
        - in "select *" queries the * expanded correctly according to
          ANSI for arbitrary natural/using joins
        - natural/using joins are correctly transformed into JOIN ... ON
          for any number/nesting of the joins.
        - column references are correctly resolved against natural joins
          of any nesting and combined with arbitrary other joins.
      
      * This patch also contains a fix for name resolution of items
        inside the ON condition of JOIN ... ON - in this case items must
        be resolved only against the JOIN operands. To support such
        'local' name resolution, the patch introduces a stack of
        name resolution contexts used at parse time.
      
      NOTICE:
      - This patch is not complete in the sense that
        - there are 2 test cases that still do not pass -
          one in join.test, one in select.test. Both are marked
          with a comment "TODO: WL#2486".
        - it does not include a new test specific for the task
      a247282a
  15. 10 Aug, 2005 3 commits
  16. 08 Aug, 2005 1 commit
  17. 28 Jul, 2005 1 commit
  18. 20 Jul, 2005 2 commits
  19. 19 Jul, 2005 3 commits
  20. 18 Jul, 2005 1 commit
    • monty@mishka.local's avatar
      Cleanups during review · 78c65b5a
      monty@mishka.local authored
      Changed defaults option --instance to --defaults-group-suffix
      Changed option handling to allow --defaults-file, --defaults-extra-file and --defaults-group-suffix to be given in any order
      Changed MYSQL_INSTANCE to MYSQL_GROUP_SUFFIX
      mysql_print_defaults now understands --defaults-group-suffix
      Remove usage of my_tempnam() (not safe function)
      if( -> if ( and while( to while (
      78c65b5a
  21. 16 Jul, 2005 1 commit
  22. 15 Jul, 2005 2 commits
  23. 14 Jul, 2005 4 commits
  24. 13 Jul, 2005 2 commits
  25. 12 Jul, 2005 3 commits
  26. 01 Jul, 2005 2 commits