1. 09 Jan, 2007 2 commits
  2. 11 Nov, 2006 1 commit
  3. 10 Nov, 2006 6 commits
  4. 09 Nov, 2006 1 commit
    • joerg@trift2.'s avatar
      mysql-test/install_test_db.sh · dce6efd0
      joerg@trift2. authored
          Adapt to the different path of the server program, if installation was by RPM.
          Missing in the first changeset for bug#17194.
      dce6efd0
  5. 08 Nov, 2006 2 commits
  6. 07 Nov, 2006 3 commits
  7. 05 Nov, 2006 2 commits
  8. 03 Nov, 2006 4 commits
  9. 02 Nov, 2006 8 commits
  10. 01 Nov, 2006 6 commits
    • kostja@bodhi.local's avatar
      Merge bk-internal.mysql.com:/home/bk/mysql-4.1 · 6a28c436
      kostja@bodhi.local authored
      into  bodhi.local:/opt/local/work/mysql-4.1-runtime
      6a28c436
    • joerg@trift2.'s avatar
      mysql-test/mysql-test-run.pl + mysql-test/mysql-test-run.sh · de9e7596
      joerg@trift2. authored
      Necessary changes if one of the test scripts is to be used with a RPM installation (bug#17194).
      
      This change handles finding the server and the other programs,
      but it does not solve the problem to get a writable "var" directory.
      If we want to avoid world-writable directories below "/usr/share/mysql-test" (and we do!), 
      any automatic solution would require fixed decisions which may not match the local installation.
      
      For the Perl script, use "--vardir"; for the shell script, create "mysql-test/var" manually.
      de9e7596
    • msvensson@shellback.(none)'s avatar
      Merge bk-internal:/home/bk/mysql-4.1-maint · 8d29d65c
      msvensson@shellback.(none) authored
      into  shellback.(none):/home/msvensson/mysql/mysql-4.1-maint
      8d29d65c
    • msvensson@shellback.(none)'s avatar
      Merge 192.168.0.10:mysql/mysql-4.1-maint · c4369f24
      msvensson@shellback.(none) authored
      into  shellback.(none):/home/msvensson/mysql/mysql-4.1-maint
      c4369f24
    • petr/cps@mysql.com/owlet.local's avatar
      Fix Bug #9191 "TIMESTAMP/from_unixtime() no longer accepts 2^31-1" · 3ec542df
      petr/cps@mysql.com/owlet.local authored
      (4.1 version, with post-review fixes)
        
        The fix for another Bug (6439) limited FROM_UNIXTIME() to
        TIMESTAMP_MAX_VALUE which is 2145916799 or 2037-12-01 23:59:59 GMT,
        however unix timestamp in general is not considered to be limited 
        by this value. All dates up to power(2,31)-1 are valid.
        
        This patch extends allowed TIMESTAMP range so, that max
        TIMESTAMP value is power(2,31)-1. It also corrects
        FROM_UNIXTIME() and UNIX_TIMESTAMP() functions, so that
        max allowed UNIX_TIMESTAMP() is power(2,31)-1. FROM_UNIXTIME()
        is fixed accordingly to allow conversion of dates up to
        2038-01-19 03:14:07 UTC. The patch also fixes CONVERT_TZ()
        function to allow extended range of dates.
        
        The main problem solved in the patch is possible overflows
        of variables, used in broken-time representation to time_t
        conversion (required for UNIX_TIMESTAMP).
      3ec542df
    • thek@kpdesk.mysql.com's avatar
      Merge kpdesk.mysql.com:/home/thek/dev/bug22828/my41-bug22828 · df82f584
      thek@kpdesk.mysql.com authored
      into  kpdesk.mysql.com:/home/thek/dev/mysql-4.1-maint
      df82f584
  11. 31 Oct, 2006 5 commits