An error occurred fetching the project authors.
  1. 14 Sep, 2005 3 commits
  2. 13 Sep, 2005 1 commit
    • gluh@eagle.intranet.mysql.r18.ru's avatar
      Bug#9683 INFORMATION_SCH: Creation of temporary table allowed in · cc395fc0
      gluh@eagle.intranet.mysql.r18.ru authored
               Information_schema DB 
      Bug#9846 Inappropriate error displayed while
               dropping table from 'INFORMATION_SCHEMA'
      Bug#10734 Grant of privileges other than 'select' and 
               'create view' should fail on schema 
      Bug#10708 SP's can use INFORMATION_SCHEMA as ROUTINE_SCHEMA
      
       cumulative fix for bugs above(after review, 2nd version)
       added privilege check for information schema db & tables
      cc395fc0
  3. 12 Sep, 2005 1 commit
    • timour@mysql.com's avatar
      Fix for BUG#6808. · 9d862db7
      timour@mysql.com authored
      The problem was in that add_table_to_list was testing for duplicate tables
      in a list of tables that included the created view.
      9d862db7
  4. 10 Sep, 2005 2 commits
    • lars@mysql.com's avatar
      eff11c53
    • timour@mysql.com's avatar
      Fix for BUG#12943. · 7d24bdac
      timour@mysql.com authored
      The problem was that in the first production in rule 'join_table', that
      processes simple cross joins, the parser was processing the second join operand
      before the first one due to unspecified priorities of JOINs. As a result in the
      case of cross joins the parser constructed a tree with incorrect nesting:
      the expression "t1 join t2 join t3 on some_cond" was interpreted as
      "t1 join (t2 join t3 on some_cond)" instead of
      "(t1 join t2) join t3 on some_cond".
      Because of this incorrect nesting the method make_join_on_context picked an
      incorrect table as the first table of the name resolution context.
      
      The solution assignes correct priorities to the related production.
      7d24bdac
  5. 09 Sep, 2005 1 commit
  6. 07 Sep, 2005 1 commit
  7. 05 Sep, 2005 1 commit
  8. 03 Sep, 2005 1 commit
  9. 02 Sep, 2005 2 commits
    • konstantin@mysql.com's avatar
      Implement WL#2661 "Prepared Statements: Dynamic SQL in Stored Procedures". · 38486e83
      konstantin@mysql.com authored
      The idea of the patch is to separate statement processing logic,
      such as parsing, validation of the parsed tree, execution and cleanup, 
      from global query processing logic, such as logging, resetting
      priorities of a thread, resetting stored procedure cache, resetting
      thread count of errors and warnings.
      This makes PREPARE and EXECUTE behave similarly to the rest of SQL
      statements and allows their use in stored procedures.
      This patch contains a change in behaviour:
      until recently for each SQL prepared statement command, 2 queries
      were written to the general log, e.g.
      [Query]   prepare stmt from @stmt_text;
      [Prepare] select * from t1 <-- contents of @stmt_text
      The chagne was necessary to prevent [Prepare] commands from being written
      to the general log when executing a stored procedure with Dynamic SQL.
      We should consider whether the old behavior is preferrable and probably
      restore it.
      This patch refixes Bug#7115, Bug#10975 (partially), Bug#10605 (various bugs
      in Dynamic SQL reported before it was disabled).
      38486e83
    • konstantin@mysql.com's avatar
      Rename: · a3ddcdf8
      konstantin@mysql.com authored
      - current_arena to stmt_arena: the thread may have more than one
      'current' arenas: one for runtime data, and one for the parsed 
      tree of a statement. Only one of them is active at any moment.
      - set_item_arena -> set_query_arena, because Item_arena was renamed to 
      Query_arena a while ago
      - set_n_backup_item_arena -> set_n_backup_active_arena;
      the active arena is the arena thd->mem_root and thd->free_list
      are currently pointing at.
      - restore_backup_item_arena -> restore_active_arena (with the same
      rationale)
      - change_arena_if_needed -> activate_stmt_arena_if_needed; this
      method sets thd->stmt_arena active if it's not done yet.
      a3ddcdf8
  10. 01 Sep, 2005 3 commits
  11. 31 Aug, 2005 2 commits
    • lars@mysql.com's avatar
      BUG#12542: All set statements should be executed by slave thd · 7fd89c85
      lars@mysql.com authored
      rpl_replicate_do.result:
        New test case
      sql_parse.cc:
        All SET statements should be executed by slave thd
      rpl_replicate_do.test:
        New test case
      7fd89c85
    • bar@mysql.com's avatar
      · f2ea1ac8
      bar@mysql.com authored
        bug#9948 changed client-charset behavior in 4.1.x libmysql, which issue BC prob
      
      sql_parse.cc:
      mysqld.cc:
      
        Added --skip-client-character-set-handshake.
        When this option is activated, client side character set
        (which is sent in handshake) is ignored, and server side
        default-character-set value is used for character_set_client
        and character_set_results, thus reprodicing 4.0 behaviour.
      f2ea1ac8
  12. 30 Aug, 2005 1 commit
  13. 29 Aug, 2005 2 commits
  14. 26 Aug, 2005 1 commit
  15. 25 Aug, 2005 1 commit
  16. 24 Aug, 2005 1 commit
  17. 23 Aug, 2005 1 commit
  18. 21 Aug, 2005 1 commit
  19. 20 Aug, 2005 1 commit
  20. 19 Aug, 2005 1 commit
  21. 18 Aug, 2005 1 commit
  22. 15 Aug, 2005 3 commits
  23. 13 Aug, 2005 1 commit
    • tsmith@.mysql.com's avatar
      sql_parse.cc: · 9097bd2f
      tsmith@.mysql.com authored
        Don't skip SET command even if --replicate-wild* says to.
        E.g., SET ONE_SHOT TIME_ZONE = 'XYZ' should be executed (BUG #12542)
      9097bd2f
  24. 12 Aug, 2005 4 commits
    • serg@sergbook.mysql.com's avatar
      BUG#12162 - one can start two transactions with the same XID. · f5ff607c
      serg@sergbook.mysql.com authored
      Now we keep all active XID's in a hash
      f5ff607c
    • 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
    • monty@mysql.com's avatar
      Fixes during review of new pushed code · 4c0d23e1
      monty@mysql.com authored
      Removed duplicate usage of TMP_TABLE_FORCE_MYISAM by making 'options' longlong
      4c0d23e1
    • jimw@mysql.com's avatar
      Avoid spurious error when restoring INFORMATION_SCHEMA as the current · 3a815f45
      jimw@mysql.com authored
      database after failing to execute a stored procedure in an inaccessible
      database. (Bug #12318)
      3a815f45
  25. 11 Aug, 2005 1 commit
  26. 10 Aug, 2005 2 commits