An error occurred fetching the project authors.
  1. 10 Nov, 2005 2 commits
  2. 02 Nov, 2005 1 commit
  3. 31 Oct, 2005 1 commit
  4. 27 Oct, 2005 2 commits
  5. 21 Oct, 2005 1 commit
  6. 19 Oct, 2005 1 commit
  7. 17 Oct, 2005 1 commit
    • guilhem@mysql.com's avatar
      Fix for BUG#4544 "read_only also affects temporary tables": · b386fef1
      guilhem@mysql.com authored
      the READ_ONLY global variable now allows statements which are to update only temporary tables
      (note: if a statement, after parse stage, looks like it will update a non-temp table, it will be rejected,
      even if at execution it would have turned out that 0 rows would be updated; for example
      UPDATE my_non_tem_table SET a=1 WHERE 1 = 0; will be rejected).
      b386fef1
  8. 13 Oct, 2005 1 commit
  9. 12 Oct, 2005 1 commit
  10. 11 Oct, 2005 2 commits
    • monty@mysql.com's avatar
      Reviewing new pushed code · f5fdf3e8
      monty@mysql.com authored
      - CHAR() now returns binary string as default
      - CHAR(X*65536+Y*256+Z) is now equal to CHAR(X,Y,Z) independent of the character set for CHAR()
      - Test for both ETIMEDOUT and ETIME from pthread_cond_timedwait()
        (Some old systems returns ETIME and it's safer to test for both values
         than to try to write a wrapper for each old system)
      - Fixed new introduced bug in NOT BETWEEN X and X
      - Ensure we call commit_by_xid or rollback_by_xid for all engines, even if one engine has failed
      - Use octet2hex() for all conversion of string to hex
      - Simplify and optimize code
      f5fdf3e8
    • hf@deer.(none)'s avatar
  11. 10 Oct, 2005 4 commits
  12. 08 Oct, 2005 2 commits
  13. 07 Oct, 2005 1 commit
  14. 06 Oct, 2005 1 commit
    • monty@mysql.com's avatar
      Review of code pushed since last 5.0 pull: · 78e828d3
      monty@mysql.com authored
      Ensure that ccache is also used for C programs
      mysql: Ensure that 'delimiter' works the same way in batch mode as in normal mode
      mysqldump: Change to use ;; (instead of //) as a stored procedure/trigger delimiter
      Fixed test cases by adding missing DROP's and rename views to be of type 'v#'
      Removed MY_UNIX_PATH from fn_format()
      Removed current_db_used from TABLE_LIST
      Removed usage of 'current_thd' in Item_splocal
      Removed some compiler warnings
      A bit faster longlong2str code
      78e828d3
  15. 05 Oct, 2005 1 commit
  16. 30 Sep, 2005 1 commit
  17. 28 Sep, 2005 1 commit
  18. 23 Sep, 2005 1 commit
  19. 21 Sep, 2005 2 commits
  20. 20 Sep, 2005 1 commit
  21. 19 Sep, 2005 1 commit
  22. 15 Sep, 2005 1 commit
  23. 14 Sep, 2005 4 commits
  24. 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
  25. 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
  26. 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
  27. 09 Sep, 2005 1 commit
  28. 07 Sep, 2005 1 commit