1. 28 Jun, 2006 1 commit
    • unknown's avatar
      Bug#19857: When a user with CREATE ROUTINE priv creates a routine it results in NULL p/w · 5312b349
      unknown authored
        
      sp_grant_privileges(), the function that GRANTs EXECUTE + ALTER privs on a SP,
      did so creating a user-entry with not password; mysql_routine_grant() would then
      write that "change" to the user-table.
      
      
      mysql-test/r/sp-security.result:
        prove that creating a stored procedure will not destroy the creator's password
      mysql-test/t/sp-security.test:
        prove that creating a stored procedure will not destroy the creator's password
      sql/sql_acl.cc:
        get password from ACLs, convert to correct format, and use it when
        forcing GRANTS for SPs
      5312b349
  2. 26 Jun, 2006 3 commits
  3. 24 Jun, 2006 2 commits
    • unknown's avatar
      Merge knielsen@10.100.52.19:/usr/local/mysql/tmp-5.0 · 9d7799e7
      unknown authored
      into  mysql.com:/data0/knielsen/tmp-5.0
      
      
      9d7799e7
    • unknown's avatar
      Fix race condition in test case wait_timeout. · 4a9a0b9a
      unknown authored
      Sometimes the helper connection (that is watching for the main connection
      to time out) would itself time out first, causing the test to fail.
      
      
      mysql-test/t/wait_timeout.test:
        Increase connection timeout in connection wait_con so we will not loose
        the connection that is watching for the real wait_timeout to trigger.
      4a9a0b9a
  4. 23 Jun, 2006 7 commits
  5. 22 Jun, 2006 14 commits
    • unknown's avatar
      mysql.spec.sh: · 92ad3d5b
      unknown authored
        Disable the simplistic auto dependency scan for test/bench (bug#20078)
      
      
      support-files/mysql.spec.sh:
        Disable the simplistic auto dependency scan for test/bench (bug#20078)
      92ad3d5b
    • unknown's avatar
      Bug#20588: mysqldump.test may fail, depending on system-wide configuration · df4ba783
      unknown authored
      mysqldump.test calls my_print_defaults in a way that includes the systemwide
      my.cnf, so the results will be beyond our control and depend on whatever the
      user has in their my.cnf, namely the [mysqldump] section.
      
      call my_print_defaults with --config-file rather than --defaults-extra-file
      to prevent inclusion of system-wide defaults and use our config-file only.
      
      
      mysql-test/t/mysqldump.test:
        call my_print_defaults with our setup only, do not include the systemwide
        my.cnf as that would make the results unpredictable.
      df4ba783
    • unknown's avatar
      Merge bk-internal.mysql.com:/home/bk/mysql-5.0-maint · 357755fc
      unknown authored
      into  mysql.com:/home/tnurnberg/mysql-5.0-maint-19409
      
      
      357755fc
    • unknown's avatar
      Merge bk-internal.mysql.com:/home/bk/mysql-5.0 · 0f0e518e
      unknown authored
      into  mysql.com:/opt/local/work/mysql-5.0-runtime
      
      
      0f0e518e
    • unknown's avatar
      Merge clam.ndb.mysql.com:/space/pekka/ndb/version/my50 · 1c288073
      unknown authored
      into  clam.ndb.mysql.com:/space/pekka/ndb/version/my50-bug18781
      
      
      ndb/src/kernel/blocks/dbdih/DbdihMain.cpp:
        Auto merged
      ndb/src/ndbapi/ndberror.c:
        Auto merged
      1c288073
    • unknown's avatar
      #19409: Test 'func_timestamp' fails on Windows x64 · 0271faa8
      unknown authored
      - The setting of "ENV{'TZ'}" doesn't affect the timezone
        used by MySQL Server on Windows.
      - Explicitly set timezone in test cases before doing UTC/localtime
        conversions so tests produce deterministic results
      
      
      mysql-test/r/func_timestamp.result:
        Update test results
      mysql-test/r/type_timestamp.result:
        Update test results
      mysql-test/t/func_timestamp.test:
        Specifically set timezone to make tests that do localtime/UTC conversions deterministic
      mysql-test/t/type_timestamp.test:
        Specifically set timezone to make tests that do localtime/UTC conversions deterministic
      0271faa8
    • unknown's avatar
      Bug#19408 Test 'func_time' fails on Windows x64 · e8beb72c
      unknown authored
      - The setting of "ENV{'TZ'}" doesn't affect the timezone
        used by MySQL Server on Windows.
      - Explicitly set timezone to "+03:00" in test case before
        doing the calculatiosn to check that there is three hours
        difference between utc and local time.
      (Magnus' fix)
      
      
      mysql-test/r/func_time.result:
        Update test results
      mysql-test/t/func_time.test:
        Set timezone to GMT-3, to make it possible to use "interval 3 hour"
      e8beb72c
    • unknown's avatar
      Merge mysql.com:/home/tomash/src/mysql_ab/mysql-5.0 · dca36865
      unknown authored
      into  mysql.com:/home/tomash/src/mysql_ab/mysql-5.0-bug15811
      
      
      dca36865
    • unknown's avatar
      Merge mysql.com:/opt/local/work/mysql-5.0-root · 8eb00d0a
      unknown authored
      into  mysql.com:/opt/local/work/mysql-5.0-runtime
      
      
      8eb00d0a
    • unknown's avatar
      Merge mysql.com:/home/tomash/src/mysql_ab/mysql-5.0 · a887fa9e
      unknown authored
      into  mysql.com:/home/tomash/src/mysql_ab/mysql-5.0-bug15811
      
      
      a887fa9e
    • unknown's avatar
      A fix and a test case for Bug#15217 "Using a SP cursor on a table created · 67fd3c4a
      unknown authored
       with PREPARE fails with weird error".
      More generally, re-executing a stored procedure with a complex SP cursor query
      could lead to a crash.
      
      The cause of the problem was that SP cursor queries were not optimized 
      properly at first execution: their parse tree belongs to sp_instr_cpush,
      not sp_instr_copen, and thus the tree was tagged "EXECUTED" when the
      cursor was declared, not when it was opened. This led to loss of optimization
      transformations performed at first execution, as sp_instr_copen saw that the
      query is already "EXECUTED" and therefore either not ran first-execution 
      related blocks or wrongly rolled back the transformations caused by 
      first-execution code.
      The fix is to update the state of the parsed tree only when the tree is
      executed, as opposed to when the instruction containing the tree is executed.
      Assignment if i->state is moved to reset_lex_and_exec_core.
      
      
      mysql-test/r/sp.result:
        Test results fixed (Bug#15217)
      mysql-test/t/sp.test:
        Add a test case for Bug#15217
      sql/sp_head.cc:
        Move assignment of stmt_arena->state to reset_lex_and_exec_core
      67fd3c4a
    • unknown's avatar
      Bug#15811: extremely long time for mysql client to execute long INSERT · 15ac6406
      unknown authored
      The problem was in redundant calls to strlen() in string functions,
      where we may then return after checking only the small number of characters.
      
      No test case is provided since it's a performance fix.
      
      
      strings/ctype-mb.c:
        Do not use strlen() where arbitrary horizon of at least
        CHARSET_INFO::mbmaxlen character is sufficient.
      15ac6406
    • unknown's avatar
      Merge epotemkin@bk-internal.mysql.com:/home/bk/mysql-5.0 · 6e8cb4d6
      unknown authored
      into moonbone.local:/work/tmp_merge-5.0-opt-mysql
      
      
      6e8cb4d6
    • unknown's avatar
      Merge bk-internal.mysql.com:/home/bk/mysql-5.0-maint · 41af8b9e
      unknown authored
      into  zippy.(none):/home/cmiller/work/mysql/mysql-5.0__bug19904
      
      
      41af8b9e
  6. 21 Jun, 2006 13 commits