An error occurred fetching the project authors.
  1. 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
  2. 19 Aug, 2005 1 commit
  3. 18 Aug, 2005 3 commits
  4. 13 Aug, 2005 1 commit
    • sanja@hasky.mysql.fi's avatar
      table.cc: · 562786bc
      sanja@hasky.mysql.fi authored
        remove unneeded multitable_view assignment
      sql_view.cc:
        fix potential memorry overrun in ref_array
        asssign multitable_view in time of view creation (BUG#12569)
      562786bc
  5. 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
  6. 27 Jul, 2005 1 commit
  7. 22 Jul, 2005 1 commit
  8. 01 Jul, 2005 1 commit
  9. 22 Jun, 2005 2 commits
  10. 19 Jun, 2005 1 commit
    • svoj@mysql.com's avatar
      WL#2286 - Compile MySQL w/YASSL support · 7660f609
      svoj@mysql.com authored
      Fix for yaSSL link failures with Forte Developer 7, MIPSpro Compilers, Compaq C++.
      These compilers have problem with implicit template instantiation in archives
      (libyassl.a, libtaocrypt.a). Instantiate templates explicitly.
      
      Fix for yaSSL link failure on powermacg5 (gcc 3.3). When -O3 is specified gcc inlines
      __cxa_pure_virtual. This is wrong behavior, __cxa_pure_virtual must never be inlined.
      7660f609
  11. 17 Jun, 2005 2 commits
  12. 15 Jun, 2005 1 commit
    • serg@serg.mylan's avatar
      renamed: · 01b3c709
      serg@serg.mylan authored
        Item_buff -> Cached_item
        Item_arena -> Query_arena
        TEST_ASSERT -> YYERROR_UNLESS
      01b3c709
  13. 01 Jun, 2005 1 commit
  14. 31 May, 2005 1 commit
  15. 26 May, 2005 2 commits
    • pem@mysql.comhem.se's avatar
      Fixed BUG#9937: Crash on call to stored procedure. · 3eca4bf2
      pem@mysql.comhem.se authored
      This only showed up on two known platforms, both ia64 (one HP-UX and one Linux wich icc).
      For some reason, they only get half the stack size they are supposed to have, which
      makes deep SP recursion overrun the stack before check_stack_overrun() is triggered.
      Also made som minor fixes in the check_stack_overrun() definition, supporting variable
      margins.
      No test case added, but the reason for the bug report was a failed existing test case
      on these machines, which now works.
      3eca4bf2
    • monty@mysql.com's avatar
      Moved detection of wrong decimal fields before decimal field was created to... · 206c0ebb
      monty@mysql.com authored
      Moved detection of wrong decimal fields before decimal field was created to avoid ASSERT() for DECIMAL(1)
      206c0ebb
  16. 25 May, 2005 1 commit
  17. 18 May, 2005 1 commit
  18. 10 May, 2005 1 commit
    • igor@rurik.mysql.com's avatar
      Many files: · 9d4b228b
      igor@rurik.mysql.com authored
        Fixed bug #8528.
        Representation for single-table views was made similar to
        representation for multi-table views.
      view.test:
        Added test case for bug #8528.
      view.result:
        Added test case for bug #8528. Fixed other test cases.
      9d4b228b
  19. 07 May, 2005 1 commit
  20. 12 Apr, 2005 1 commit
  21. 02 Apr, 2005 1 commit
  22. 31 Mar, 2005 1 commit
  23. 22 Mar, 2005 2 commits
  24. 15 Mar, 2005 1 commit
  25. 03 Mar, 2005 1 commit
  26. 26 Feb, 2005 1 commit
  27. 23 Feb, 2005 1 commit
  28. 15 Feb, 2005 1 commit
  29. 11 Feb, 2005 3 commits
    • igor@rurik.mysql.com's avatar
      select.result: · 634424ca
      igor@rurik.mysql.com authored
        After revision of the fix for bug #7520.
      table.cc:
        Revised the fix for bug #7520.
        Made it compliant with 5.0 code where the bug does not exist.
      634424ca
    • ingo@mysql.com's avatar
      After merge fix. · 46e6b73b
      ingo@mysql.com authored
      46e6b73b
    • igor@rurik.mysql.com's avatar
      select.result, select.test: · 8b3d59ad
      igor@rurik.mysql.com authored
        Added a test case for bug #7520.
      table.cc:
        Fixed bug #7520.
        The bug was caused by a wrong calculation of the field max_key_length for
        a TABLE structure when there was an index on a blob field.
      8b3d59ad
  30. 10 Feb, 2005 1 commit
  31. 31 Jan, 2005 1 commit
  32. 26 Jan, 2005 1 commit