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. 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
  3. 10 Aug, 2005 3 commits
  4. 08 Aug, 2005 1 commit
  5. 28 Jul, 2005 1 commit
  6. 20 Jul, 2005 2 commits
  7. 19 Jul, 2005 3 commits
  8. 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
  9. 16 Jul, 2005 1 commit
  10. 15 Jul, 2005 2 commits
  11. 14 Jul, 2005 4 commits
  12. 13 Jul, 2005 2 commits
  13. 12 Jul, 2005 3 commits
  14. 01 Jul, 2005 2 commits
  15. 30 Jun, 2005 1 commit
    • konstantin@mysql.com's avatar
      A fix and a test case for Bug#10794 "mysql_stmt_attr_set no · f60ebc48
      konstantin@mysql.com authored
      open cursor after mysql_stmt_execute" + post-review fixes.
      The bug was caused by wrong flags in stmt->server_status on the client
      side: if there was no cursor, the server didn't send server_status
      flags to the client, and the old flags were used to set up the
      fetch function of a statement. Consequently, stmt_read_row_from_cursor was
      used when there was no cursor. The fix fixes the server to always
      send server flags to the client.
      f60ebc48
  16. 28 Jun, 2005 1 commit
    • konstantin@mysql.com's avatar
      A fix and a test case for Bug#10736 "mysql_stmt_attr_set · 8b0cee88
      konstantin@mysql.com authored
      CURSOR_TYPE_READ_ONLY select within select".
      The bug was caused by the reset of thd->mem_root to thd->main_mem_root in 
      Item_subselect::exec, which in turn triggered too early free_root() for
      data which was needed on subsequent fetches from a cursor.
      This reset also caused a memory leak in stored procedures, as 
      subsequent executions of instructions containing a subselect
      were allocating memory in thd->main_mem_root, which is not freed
      until the end of the entire SP, instead of the per-call mem_root,
      which is freed in the end of execution of the instruction.
      8b0cee88
  17. 24 Jun, 2005 1 commit
  18. 20 Jun, 2005 1 commit
  19. 19 Jun, 2005 2 commits
  20. 17 Jun, 2005 1 commit
  21. 14 Jun, 2005 2 commits
  22. 09 Jun, 2005 1 commit
  23. 01 Jun, 2005 1 commit
  24. 27 May, 2005 1 commit
  25. 18 May, 2005 1 commit