1. 13 Dec, 2007 1 commit
  2. 10 Dec, 2007 1 commit
  3. 06 Dec, 2007 1 commit
  4. 05 Dec, 2007 1 commit
  5. 01 Dec, 2007 2 commits
  6. 30 Nov, 2007 5 commits
    • unknown's avatar
      Merge four.local.lan:/work/merge/mysql-4.1-dev · d09dfdab
      unknown authored
      into  four.local.lan:/work/trees/mysql-4.1-build-src-clean
      
      
      d09dfdab
    • unknown's avatar
      Merge mysql.com:/home/hf/work/31900/my41-31900 · d87a75c1
      unknown authored
      into  mysql.com:/home/hf/work/mrg/my41-mrg
      
      
      d87a75c1
    • unknown's avatar
      Fix for · 56b00941
      unknown authored
         Bug#31030 rpl000015.test fails if $MYSQL_TCP_PORT != 3306
      Note:
        This bug does not occur in MySQL 5.0 and up, because
        ChangeSet 1.2328.2.1 2006/11/27 for MySQL 5.0 prevents this.
        The 5.0 fix uses the environment variable DEFAULT_MASTER_PORT
        which is set by mysql-test-run.pl.
        mysql-test-run.pl in 4.1 does not set this variable.
        There are two alternatives:
        1) Backport the 5.0 fix for this test including modifications
           to mysql-test-run.pl and mysql-test-run-shell.
           This is a not acceptable impact on an old MySQL version.
        2) Fix the problem different than in 5.0 like in the current
           ChangeSet + do not apply these changes when upmerging to 5.0
      
      
      mysql-test/r/rpl000015.result:
        Updated result
      mysql-test/t/disabled.def:
        Enable rpl000015
      mysql-test/t/rpl000015.test:
        Unify the MASTER_PORT number
      56b00941
    • unknown's avatar
      my_global.h: · 44ebdc09
      unknown authored
        Added 64 bit Mac OS X hard coded settings, for universal binaries
      
      
      include/my_global.h:
        Added 64 bit Mac OS X hard coded settings, for universal binaries
      44ebdc09
    • unknown's avatar
  7. 29 Nov, 2007 2 commits
    • unknown's avatar
      my_global.h: · f177f5f9
      unknown authored
        Added 64 bit Mac OS X hard coded settings, for universal binaries
      
      
      include/my_global.h:
        Added 64 bit Mac OS X hard coded settings, for universal binaries
      f177f5f9
    • unknown's avatar
      Bug #29085 A small double precision number becomes zero. · 23e402bf
      unknown authored
      Denormalized DOUBLE-s can't be properly handled by old MIPS processors.
      So we need to enable specific mode for them so IRIX will do use
      software round to handle such numbers. 
      
      
      sql/mysqld.cc:
        Bug #29085 A small double precision number becomes zero.
        
        reset_floating_point_exeption() renamed as set_proper_floating_point_mode()
        #ifdef __sgi code added to enable denormalized DOUBLE-s on IRIX
      23e402bf
  8. 27 Nov, 2007 1 commit
    • unknown's avatar
      Bug#32707: misdimensioned buffer in protocol layer · 7c0db983
      unknown authored
      Miscalculation in protocol-layer: size buffer correctly so
      even really long error messages cannot overflow our buffer.
      
      
      sql/protocol.cc:
        size buffer correctly so really long error messages cannot overflow it.
      7c0db983
  9. 26 Nov, 2007 1 commit
  10. 24 Nov, 2007 1 commit
  11. 21 Nov, 2007 1 commit
  12. 20 Nov, 2007 1 commit
  13. 19 Nov, 2007 1 commit
    • unknown's avatar
      Bug #30284 spatial key corruption. · da1efa33
      unknown authored
      SPATIAL key is fine actually, but the chk_key() function
      mistakenly returns error. It tries to compare checksums
      of btree and SPATIAL keys while the checksum for the SPATIAL isn't
      calculated (always 0). Same thing with FULLTEXT keys is handled
      using full_text_keys counter, so fixed by counting both
      SPATIAL and FULLTEXT keys in that counter.
      
      
      myisam/mi_check.c:
        Bug #30284 spatial key corruption
        
        full_text_keys counts both FULL_TEXT and SPATIAL keys
      mysql-test/r/gis.result:
        Bug #30284 spatial key corruption
        
        test result
      mysql-test/t/gis.test:
        Bug #30284 spatial key corruption.
        
        test case
      da1efa33
  14. 17 Nov, 2007 1 commit
  15. 16 Nov, 2007 2 commits
  16. 14 Nov, 2007 5 commits
  17. 13 Nov, 2007 2 commits
    • unknown's avatar
      Merge bk@192.168.21.1:mysql-4.1-opt · 9248b402
      unknown authored
      into  mysql.com:/home/hf/work/31305/my41-31305
      
      
      9248b402
    • unknown's avatar
      Bug #31158 Spatial, Union, LONGBLOB vs BLOB bug (crops data) · eb347921
      unknown authored
      max_length parameter for BLOB-returning functions must be big enough
      for any possible content. Otherwise the field created for a table
      will be too small.
      
      
      mysql-test/r/gis.result:
        Bug #31158  Spatial, Union, LONGBLOB vs BLOB bug (crops data)
        
        test result
      mysql-test/t/gis.test:
        Bug #31158  Spatial, Union, LONGBLOB vs BLOB bug (crops data)
        
        test case
      sql/field.cc:
        Bug #31158  Spatial, Union, LONGBLOB vs BLOB bug (crops data)
        
        max_field_size used instead of numeric value
      sql/field.h:
        Bug #31158  Spatial, Union, LONGBLOB vs BLOB bug (crops data)
        
        max_field_size constant defined
      sql/item_geofunc.cc:
        Bug #31158  Spatial, Union, LONGBLOB vs BLOB bug (crops data)
        
        max_length parameter fixed
      eb347921
  18. 12 Nov, 2007 7 commits
    • unknown's avatar
      Merge kboortz@bk-internal.mysql.com:/home/bk/mysql-4.1-build · dff7a5af
      unknown authored
      into  mysql.com:/home/kent/bk/bug30069/mysql-4.1-build
      
      
      dff7a5af
    • unknown's avatar
      symlink.test, symlink.result: · 9f9ff461
      unknown authored
        Use proper variable for test.
      
      
      mysql-test/t/symlink.test:
        Use proper variable for test.
      mysql-test/r/symlink.result:
        Use proper variable for test.
      9f9ff461
    • unknown's avatar
      Merge svojtovich@bk-internal.mysql.com:/home/bk/mysql-4.0 · 12d7657e
      unknown authored
      into  mysql.com:/home/svoj/devel/mysql/BUG32111/mysql-4.0
      
      
      12d7657e
    • unknown's avatar
      bigint.test, bigint.result: · 568f6244
      unknown authored
        Test case for Bug#30069
      
      
      mysql-test/r/bigint.result:
        Test case for Bug#30069
      mysql-test/t/bigint.test:
        Test case for Bug#30069
      568f6244
    • unknown's avatar
      After merge fix. · 88701b45
      unknown authored
      88701b45
    • unknown's avatar
      Merge mysql.com:/home/svoj/devel/mysql/BUG32111/mysql-4.0 · a1e38552
      unknown authored
      into  mysql.com:/home/svoj/devel/mysql/BUG32111/mysql-4.1-engines
      
      
      mysys/my_symlink2.c:
        Auto merged
      mysql-test/r/symlink.result:
        SCCS merged
      mysql-test/t/symlink.test:
        SCCS merged
      a1e38552
    • unknown's avatar
      Bug #31305 myisam tables crash when they are near capacity. · cb927e2f
      unknown authored
      When we insert a record into MYISAM table which is almost 'full',
      we first write record data in the free space inside a file, and then
      check if we have enough space after the end of the file.
      So if we don't have the space, table will left corrupted.
      Similar error also happens when we updata MYISAM tables.
      
      Fixed by modifying write_dynamic_record and update_dynamic_record functions
      to check for free space before writing parts of a record
      
      
      BitKeeper/etc/ignore:
        Added libmysql_r/client_settings.h libmysqld/ha_blackhole.cc to the ignore list
      myisam/mi_dynrec.c:
        Bug #31305 myisam tables crash when they are near capacity.
        
        now we check space left in table in write_dynamic_record
        and update_dynamic_record functions.
        If we don't have enough room for the new (updated) record, return with the
        error.
      mysql-test/r/almost_full.result:
        New BitKeeper file ``mysql-test/r/almost_full.result''
      mysql-test/t/almost_full.test:
        New BitKeeper file ``mysql-test/t/almost_full.test''
      cb927e2f
  19. 10 Nov, 2007 1 commit
    • unknown's avatar
      Bug #32063 "create table like" works case-significant only in "embedded" server (libmysqld) · 06323c2b
      unknown authored
      in mysql_creata_like_table() we 'downcase' the complete path to the
      .frm file. It works fine in standalone case as there usually
      we only have './' as a path to the datahome, but doesn't work in
      the embedded server where we add the real path there, so if a
      directory has uppercase letters in it's name, it won't be found.
      
      Fixed by 'downcasing' only database/table pair.
      
      
      sql/sql_table.cc:
        Bug #32063 "create table like" works case-significant only in "embedded" server (libmysqld)
        
        do not lowercase the database directory
      06323c2b
  20. 09 Nov, 2007 1 commit
    • unknown's avatar
      BUG#29083 - test suite times out on OS X 64bit - also in older releases · 5eafd5b1
      unknown authored
      The "mysql client in mysqld"(which is used by
      replication and federated) should use alarms instead of setting
      socket timeout value if the rest of the server uses alarm. By
      always calling 'my_net_set_write_timeout'
      or 'net_set_read_timeout' when changing the timeout value(s), the
      selection whether to use alarms or timeouts will be handled by
      ifdef's in those two functions.
      
      This is minimal backport of patch for BUG#26664, which was pushed
      to 5.0 and up.
      
      Affects 4.1 only.
      
      
      include/mysql_com.h:
        Move the net_set_*_timeout function declarations to mysql_com.h
      sql-common/client.c:
         Use my_net_read_timeout or my_net_write_timeout when setting the timeouts
      sql/mysql_priv.h:
        Move the net_set_*_timeout function declarations to mysql_com.h
      5eafd5b1
  21. 08 Nov, 2007 1 commit
  22. 07 Nov, 2007 1 commit
    • unknown's avatar
      Fix for bug #32103: optimizer crash when join on int and mediumint with · 0a7a55d1
      unknown authored
      variable in where clause.
      
      Problem: the new_item() method of Item_uint used an incorrect
      constructor. "new Item_uint(name, max_length)" calls
      Item_uint::Item_uint(const char *str_arg, uint length) which assumes the
      first argument to be the string representation of the value, not the
      item's name. This could result in either a server crash or incorrect
      results depending on usage scenarios.
      
      Fixed by using the correct constructor in new_item():
      Item_uint::Item_uint(const char *str_arg, longlong i, uint length).
      
      
      mysql-test/r/select.result:
        Added a test case for bug #32103.
      mysql-test/t/select.test:
        Added a test case for bug #32103.
      sql/item.h:
        Use the correct constructor for Item_uint in Item_uint::new_item().
      0a7a55d1