1. 06 May, 2008 7 commits
    • unknown's avatar
      Merge mysql.com:/Users/davi/mysql/bugs/34108-5.1 · e5491d73
      unknown authored
      into  mysql.com:/Users/davi/mysql/mysql-5.1-bugteam
      
      
      e5491d73
    • unknown's avatar
      Bug#34108 "Drop function" (test "storedproc_06") returns different message (all handlers) · b54b7c65
      unknown authored
      The problem is that the patch for Bug 33464 didn't update the
      results of the test cases which caused the problem.
      
      Dropping a stored routine also revoke privileges for all users
      on the stored routine and errors about missing grants are converted
      into warnings. Before Bug 33464 such errors could be incorrectly
      returned to the user, which would later trigger a assertion due to
      multiple errors being set.
      
      
      mysql-test/suite/funcs_1/r/innodb_storedproc_06.result:
        Update test case result, grants were already dropped.
      mysql-test/suite/funcs_1/r/memory_storedproc_06.result:
        Update test case result, grants were already dropped.
      mysql-test/suite/funcs_1/r/myisam_storedproc_06.result:
        Update test case result, grants were already dropped.
      mysql-test/suite/funcs_1/r/ndb_storedproc_06.result:
        Update test case result, grants were already dropped.
      mysql-test/suite/funcs_1/storedproc/storedproc_06.inc:
        Add comment regarding bug revealed by test case.
      mysql-test/suite/funcs_1/t/disabled.def:
        Re-enable test cases, bug has been fixed.
      b54b7c65
    • unknown's avatar
      Silence warning due to copying the address of a string constant · 2ac9a30f
      unknown authored
      into a non-const string pointer.
      
      
      client/mysqltest.c:
        Don't use a constant string as val may be modified later.
      2ac9a30f
    • unknown's avatar
      Merge bk-internal.mysql.com:/home/bk/mysql-5.1-bugteam · 9a472a21
      unknown authored
      into  mysql.com:/Users/davi/mysql/mysql-5.1-bugteam
      
      
      9a472a21
    • unknown's avatar
      Merge noir.wlan.koehntopp.de:/misc/mysql/mysql-5.0-bugteam · a7028d97
      unknown authored
      into  noir.wlan.koehntopp.de:/misc/mysql/mysql-5.1-bugteam
      
      
      mysys/my_static.c:
        Auto merged
      mysys/my_static.h:
        Auto merged
      a7028d97
    • unknown's avatar
      revert the push of bug 35616. · 65a310fe
      unknown authored
      65a310fe
    • unknown's avatar
      Bug#35616: memory overrun on 64-bit linux on setting large values for keybuffer-size · 55c336fd
      unknown authored
      We could allocate chunks larger than 4GB, but did our size-accounting in 32-bit
      values. This could lead to spurious warnings, inaccurate accounting, and, in
      theory, data loss.
      
      Affected: 64-bit platforms. Debug-build (with safemalloc). At least one buffer
      larger than 4GB. For potential data loss, a re-alloc on such a buffer would be
      necessary.
      
      
      mysys/my_static.c:
        Make memory-accounting 64-bit safe.
      mysys/my_static.h:
        Make memory-accounting 64-bit safe.
        Move in struct for better alignment when 64-bit.
      55c336fd
  2. 05 May, 2008 5 commits
  3. 02 May, 2008 8 commits
  4. 01 May, 2008 15 commits
  5. 30 Apr, 2008 5 commits