1. 03 Jan, 2005 11 commits
  2. 02 Jan, 2005 6 commits
  3. 01 Jan, 2005 6 commits
    • unknown's avatar
      Fixed failed merge · 7a18eb7a
      unknown authored
      7a18eb7a
    • unknown's avatar
      Fixed failed merge · e2d17faa
      unknown authored
      e2d17faa
    • unknown's avatar
      Merge mskold@bk-internal.mysql.com:/home/bk/mysql-4.1 · 4e6f43ac
      unknown authored
      into mysql.com:/usr/local/home/marty/MySQL/mysql-4.1
      
      
      4e6f43ac
    • unknown's avatar
      Merge kboortz@bk-internal.mysql.com:/home/bk/mysql-4.1 · 7e6dd93b
      unknown authored
      into mysql.com:/Users/kent/mysql/bk/mysql-4.1-perl
      
      
      7e6dd93b
    • unknown's avatar
      mysql-test-run.pl: · 3e2e4fb7
      unknown authored
        Added --ps-protocol and --embedded-server
      
      
      mysql-test/mysql-test-run.pl:
        Added --ps-protocol and --embedded-server
      3e2e4fb7
    • unknown's avatar
      log0recv.c: · 56db297d
      unknown authored
        Fix a wrong memset in InnoDB Hot Backup code; the bug probably did not affect anything since we do not assume that the header of a log file is filled with zeros before writing the header info there; the bug found by Felix von Leitner
      
      
      innobase/log/log0recv.c:
        Fix a wrong memset in InnoDB Hot Backup code; the bug probably did not affect anything since we do not assume that the header of a log file is filled with zeros before writing the header info there; the bug found by Felix von Leitner
      56db297d
  4. 31 Dec, 2004 13 commits
    • unknown's avatar
      Merge bk-internal.mysql.com:/home/bk/mysql-4.1 · c68b0445
      unknown authored
      into sergbook.mysql.com:/usr/home/serg/Abk/mysql-4.1
      
      
      c68b0445
    • unknown's avatar
      row0upd.c: · cd47cb56
      unknown authored
        Fix a little bug in InnoDB: we looked at the physical size of a stored SQL NULL value from a wrong field in the index; this has probably caused no bugs visible to the user, only caused some extra space usage in some rare cases; we may later backport the fix to 4.0
      
      
      innobase/row/row0upd.c:
        Fix a little bug in InnoDB: we looked at the physical size of a stored SQL NULL value from a wrong field in the index; this has probably caused no bugs visible to the user, only caused some extra space usage in some rare cases; we may later backport the fix to 4.0
      cd47cb56
    • unknown's avatar
      Merge mskold@bk-internal.mysql.com:/home/bk/mysql-4.1 · 4629c7ec
      unknown authored
      into mysql.com:/usr/local/home/marty/MySQL/mysql-4.1
      
      
      4629c7ec
    • unknown's avatar
      - updated compile-dist to include NDB cluster · 0428fcb8
      unknown authored
      
      BUILD/compile-dist:
        - make sure to include NDB cluster in the distribution, too
      0428fcb8
    • unknown's avatar
      Merge mysql.com:/space/my/mysql-4.0 · 74ddae77
      unknown authored
      into mysql.com:/space/my/mysql-4.1-build
      
      
      Build-tools/Bootstrap:
        Auto merged
      74ddae77
    • unknown's avatar
      Merge bk-internal.mysql.com:/home/bk/mysql-4.0 · f077d4b0
      unknown authored
      into sergbook.mysql.com:/usr/home/serg/Abk/mysql-4.0
      
      
      f077d4b0
    • unknown's avatar
      - Bootrap now uses "compile-dist" by default to create the source distribution · 54b76847
      unknown authored
      
      Build-tools/Bootstrap:
        - Use BUILD/compile-dist instead of compile-pentium-max
        - some minor cleanups
      54b76847
    • unknown's avatar
      post-merge · 5eaf65ab
      unknown authored
      
      mysql-test/r/grant2.result:
        new test case
      mysql-test/r/variables.result:
        don't fail w/o innodb
      mysql-test/t/grant2.test:
        new test case
      mysql-test/t/multi_update.test:
        don't fail w/o innodb
      mysql-test/t/variables.test:
        don't fail w/o innodb
      sql/sql_acl.cc:
        cleanup
      5eaf65ab
    • unknown's avatar
      Merge bk-internal.mysql.com:/home/bk/mysql-4.1 · 9bfdbc0d
      unknown authored
      into mysql.com:/home/my/mysql-4.1
      
      
      sql/mysql_priv.h:
        Auto merged
      sql/sql_insert.cc:
        Auto merged
      sql/sql_table.cc:
        Auto merged
      9bfdbc0d
    • unknown's avatar
      Remove DUP_IGNORE from enum_duplicates and instead use a separate ignore flag · 2419fa26
      unknown authored
      This allows use to use INSERT IGNORE ... ON DUPLICATE ...
      
      
      mysql-test/r/drop.result:
        safety fix
      mysql-test/t/drop.test:
        safety fix
      mysql-test/t/multi_update.test:
        ensure we cover all possible errors
      sql/log_event.cc:
        Remove DUP_IGNORE from enum_duplicates and instead use a separate ignore flag
      sql/log_event.h:
        Remove DUP_IGNORE from enum_duplicates and instead use a separate ignore flag
      sql/mysql_priv.h:
        Remove DUP_IGNORE from enum_duplicates and instead use a separate ignore flag
      sql/sql_class.h:
        Remove DUP_IGNORE from enum_duplicates and instead use a separate ignore flag
      sql/sql_delete.cc:
        Remove DUP_IGNORE from enum_duplicates and instead use a separate ignore flag
      sql/sql_insert.cc:
        Remove DUP_IGNORE from enum_duplicates and instead use a separate ignore flag
      sql/sql_lex.cc:
        Remove DUP_IGNORE from enum_duplicates and instead use a separate ignore flag
      sql/sql_lex.h:
        Remove DUP_IGNORE from enum_duplicates and instead use a separate ignore flag
      sql/sql_load.cc:
        Remove DUP_IGNORE from enum_duplicates and instead use a separate ignore flag
      sql/sql_parse.cc:
        Remove DUP_IGNORE from enum_duplicates and instead use a separate ignore flag
      sql/sql_repl.cc:
        Remove DUP_IGNORE from enum_duplicates and instead use a separate ignore flag
      sql/sql_repl.h:
        Remove DUP_IGNORE from enum_duplicates and instead use a separate ignore flag
      sql/sql_select.cc:
        Remove DUP_IGNORE from enum_duplicates and instead use a separate ignore flag
      sql/sql_table.cc:
        Remove DUP_IGNORE from enum_duplicates and instead use a separate ignore flag
      sql/sql_union.cc:
        Remove DUP_IGNORE from enum_duplicates and instead use a separate ignore flag
      sql/sql_update.cc:
        Remove DUP_IGNORE from enum_duplicates and instead use a separate ignore flag
      sql/sql_yacc.yy:
        Remove DUP_IGNORE from enum_duplicates and instead use a separate ignore flag
      2419fa26
    • unknown's avatar
      Merge lgrimmer@bk-internal.mysql.com:/home/bk/mysql-4.1 · 295c4e6a
      unknown authored
      into mysql.com:/space/my/mysql-4.1
      
      
      295c4e6a
    • unknown's avatar
      - added the "Archive", "CSV" and "Example" storage engines to the Linux · 5cde0749
      unknown authored
        "Max" RPM
      
      
      support-files/mysql.spec.sh:
        - added the "Archive", "CSV" and "Example" storage engines to the Max RPM
      5cde0749
    • unknown's avatar
      Checking size to no of free + 1 was not correct when · 90f86403
      unknown authored
      entry was released before check. Thus empty it is when
      size == no of free
      This caused a memory leak which inserted a hard limit of
      max 64 unique indexes in the cluster.
      
      
      90f86403
  5. 30 Dec, 2004 4 commits
    • unknown's avatar
      Merged fixes for bug #7297 "Two digit year should be interpreted · 0e302f5e
      unknown authored
      correctly even with zero month and day" and bug #7515 "from_unixtime(0)
      now returns NULL instead of the Epoch" into 4.1 tree.
      
      
      mysql-test/r/ps_2myisam.result:
        Updated test result after merging fix for bug #7297 "Two digit year should
        be interpreted correctly even with zero month and day" into 4.1
      mysql-test/r/ps_3innodb.result:
        Updated test result after merging fix for bug #7297 "Two digit year should
        be interpreted correctly even with zero month and day" into 4.1
      mysql-test/r/ps_4heap.result:
        Updated test result after merging fix for bug #7297 "Two digit year should
        be interpreted correctly even with zero month and day" into 4.1
      mysql-test/r/ps_5merge.result:
        Updated test result after merging fix for bug #7297 "Two digit year should
        be interpreted correctly even with zero month and day" into 4.1
      mysql-test/r/ps_6bdb.result:
        Updated test result after merging fix for bug #7297 "Two digit year should
        be interpreted correctly even with zero month and day" into 4.1
      mysql-test/r/ps_7ndb.result:
        Updated test result after merging fix for bug #7297 "Two digit year should
        be interpreted correctly even with zero month and day" into 4.1
      sql-common/my_time.c:
        Merged fix for bug #7297 "Two digit year should be interpreted correctly
        even with zero month and day" into 4.1
      sql/item_timefunc.cc:
        Small fix after merging patch solving bug #7515 "from_unixtime(0) now
        returns NULL instead of the Epoch" into 4.1.
      0e302f5e
    • unknown's avatar
      Merged bugfix · ade13078
      unknown authored
      
      BitKeeper/etc/logging_ok:
        auto-union
      sql/ha_ndbcluster.h:
        Auto merged
      ade13078
    • unknown's avatar
      merged · 379613c3
      unknown authored
      379613c3
    • unknown's avatar