1. 12 Jan, 2005 1 commit
  2. 10 Jan, 2005 1 commit
  3. 07 Jan, 2005 1 commit
    • unknown's avatar
      Bootstrap: · 04498c2a
      unknown authored
        Made the default --mail address to be <build@mysql.com>.
      
      
      Build-tools/Bootstrap:
        Made the default --mail address to be <build@mysql.com>.
      04498c2a
  4. 06 Jan, 2005 2 commits
  5. 05 Jan, 2005 1 commit
    • unknown's avatar
      Allow DEFAULT_THREAD_STACK to be set via -DDEFAULT_THREAD_STACK=... so our · 3edb7774
      unknown authored
      official binary builds for Linux that are built against a static glibc with
      a 128k thread stack size limit can be compiled with a default that doesn't
      result in a harmless (but oft-misunderstood) warning message. (Bug #6226)
      
      
      include/my_pthread.h:
        Allow DEFAULT_THREAD_STACK to be set via -DDEFAULT_THREAD_STACK=...
      3edb7774
  6. 04 Jan, 2005 1 commit
  7. 03 Jan, 2005 1 commit
  8. 31 Dec, 2004 2 commits
  9. 30 Dec, 2004 3 commits
  10. 27 Dec, 2004 2 commits
    • unknown's avatar
      row0mysql.c: · 4ba981e5
      unknown authored
        Fix the previous bug fix: dropping a table with FOREIGN KEY checks running on it caused a cascade of failed drops while the foreign key check was waiting for a lock
      
      
      innobase/row/row0mysql.c:
        Fix the previous bug fix: dropping a table with FOREIGN KEY checks running on it caused a cascade of failed drops while the foreign key check was waiting for a lock
      4ba981e5
    • unknown's avatar
      row0ins.c: · a7b984d2
      unknown authored
        Fix bug: if we dropped a table where an INSERT was waiting for a lock to check a FOREIGN KEY constraint, then an assertion would fail in lock_reset_all_on_table(), since that operation assumes no waiting locks on the table or its records
      row0mysql.c:
        Fix bug: InnoDB failed to drop a table in the background drop queue if the table was referenced by a foreign key constraint
      
      
      innobase/row/row0mysql.c:
        Fix bug: InnoDB failed to drop a table in the background drop queue if the table was referenced by a foreign key constraint
      innobase/row/row0ins.c:
        Fix bug: if we dropped a table where an INSERT was waiting for a lock to check a FOREIGN KEY constraint, then an assertion would fail in lock_reset_all_on_table(), since that operation assumes no waiting locks on the table or its records
      a7b984d2
  11. 24 Dec, 2004 1 commit
  12. 23 Dec, 2004 3 commits
    • unknown's avatar
      Merge sinisa@bk-internal.mysql.com:/home/bk/mysql-4.0 · 8feedada
      unknown authored
      into sinisa.nasamreza.org:/mnt/work/mysql-4.0
      
      
      8feedada
    • unknown's avatar
      Fix for a bug #7495 · 8ccfad76
      unknown authored
      
      mysql-test/r/func_str.result:
        result for test case for a bug in QUOTE() (Bug #7495)
      mysql-test/t/func_str.test:
        test case for a bug in QUOTE() (Bug #7495)
      sql/item_strfunc.cc:
        a better fix for a QUOTE() bug (Bug #7495)
      8ccfad76
    • unknown's avatar
      Make GRANTs, which change SSL attributes and/or user limits, · 4a5ca0bc
      unknown authored
      to behave well on 5.0 tables (well now you can't use tables from 4.1
      and 5.0 with 4.0 because former use utf8, but still it is nice to have
      similar code in acl_init() and replace_user_table()).
      This also will make such GRANTs working in 5.0 (they are broken now).
      
      
      mysql-test/r/grant.result:
        Added test for GRANT which manipulates user limits.
      mysql-test/t/grant.test:
        Added test for GRANT which manipulates user limits.
      4a5ca0bc
  13. 22 Dec, 2004 2 commits
    • unknown's avatar
      A fix for the bug #7495 · 74cc635a
      unknown authored
      
      mysql-test/r/func_str.result:
        A result for test case for the bug #7495 involving either LTRIM() 
        or TRIM() within QUOTE() function.
      mysql-test/t/func_str.test:
        A test case for the bug #7495 involving either LTRIM() or TRIM() 
        within QUOTE() function.
      sql/item_strfunc.cc:
        Changes for LTRIM() and TRIM() functions that aleviate the bug  
        entirely.
      74cc635a
    • unknown's avatar
      ha_innodb.cc: · e6dfed9f
      unknown authored
        If AUTOCOMMIT=1, do not acquire an InnoDB table lock in LOCK TABLES; this makes porting of old MyISAM applications to InnoDB easier, since in that mode InnoDB table locks caused deadlocks very easily
      
      
      sql/ha_innodb.cc:
        If AUTOCOMMIT=1, do not acquire an InnoDB table lock in LOCK TABLES; this makes porting of old MyISAM applications to InnoDB easier, since in that mode InnoDB table locks caused deadlocks very easily
      e6dfed9f
  14. 21 Dec, 2004 2 commits
    • unknown's avatar
      os0file.c: · fed35d92
      unknown authored
        Put back accidentally removed undef and remove a debug def
      
      
      innobase/os/os0file.c:
        Put back accidentally removed undef and remove a debug def
      fed35d92
    • unknown's avatar
      os0file.c: · b0d26c26
      unknown authored
        Fix InnoDB bug: on HP-UX, with a 32-bit binary, InnoDB was only able to read or write <= 2 GB files; the reason was that InnoDB treated the return value of lseek() as a 32-bit integer; lseek was used on HP-UX-11 as a replacement for pread() and pwrite() because HAVE_BROKEN_PREAD was defined on that platform
      
      
      innobase/os/os0file.c:
        Fix InnoDB bug: on HP-UX, with a 32-bit binary, InnoDB was only able to read or write <= 2 GB files; the reason was that InnoDB treated the return value of lseek() as a 32-bit integer; lseek was used on HP-UX-11 as a replacement for pread() and pwrite() because HAVE_BROKEN_PREAD was defined on that platform
      b0d26c26
  15. 20 Dec, 2004 1 commit
    • unknown's avatar
      configure.in: · 9cee9f69
      unknown authored
        Increment from 4.0.23 to 4.0.24
      
      
      configure.in:
        Increment from 4.0.23 to 4.0.24
      9cee9f69
  16. 18 Dec, 2004 5 commits
  17. 16 Dec, 2004 5 commits
  18. 13 Dec, 2004 1 commit
    • unknown's avatar
      dict0load.c: · f40f838f
      unknown authored
        dict_load_table(): detect the new table format of MySQL 5.0.3
      
      
      innobase/dict/dict0load.c:
        dict_load_table(): detect the new table format of MySQL 5.0.3
      f40f838f
  19. 11 Dec, 2004 3 commits
    • unknown's avatar
      Merge spetrunia@bk-internal.mysql.com:/home/bk/mysql-4.0 · b18e8c92
      unknown authored
      into mysql.com:/dbdata/psergey/mysql-4.0-bug6976
      
      
      b18e8c92
    • unknown's avatar
      Fix for BUG#6976: · b5c119e7
      unknown authored
      In Item_ref::Item_ref set maybe_null (and other fields fix_fields sets) to be the 
      same as in (*ref), because Item_ref::fix_fields() will not be called.  Previously 
      maybe_null was 0 always and this produced a bogus state where 
      maybe_null==0 && is_null() == true 
      which broke evaluation for some upper-level Items, like AND and OR.
      
      
      mysql-test/r/group_by.result:
        Test for BUG#6976
      mysql-test/t/group_by.test:
        Test for BUG#6976
      sql/item.cc:
        Comment added
      sql/item.h:
        Fix for BUG#6976:
          in Item_ref::Item_ref(Item**...) fix all fields because fix_fields() will not be called.
      b5c119e7
    • unknown's avatar
      Fix for BUG#5837 - attempt 3. · 8e4251dd
      unknown authored
        Call mark_as_null_row in join_read_const and join_read_system.
      
      
      mysql-test/r/multi_update.result:
        Testcase for BUG#5837
      mysql-test/t/multi_update.test:
        Testcase for BUG#5837
      sql/table.h:
        Added comments
      8e4251dd
  20. 10 Dec, 2004 2 commits
    • unknown's avatar
      Merge marko@bk-internal.mysql.com:/home/bk/mysql-4.0 · 96a927b5
      unknown authored
      into hundin.mysql.fi:/home/marko/k/mysql-4.0
      
      
      96a927b5
    • unknown's avatar
      dict0dict.h, dict0dict.c, ha_innodb.cc: · c486461e
      unknown authored
        Fix for the 0xA0 character problem in the InnoDB FOREIGN KEY parser: if my_isspace() treats 0xA0 as space, then let InnoDB do the same; this might break some multi-byte charset id's, though for big5, ujis, sjis this seems not to change the current behavior (I checked the tables in /share/charsets); this fix must NOT be merged to 4.1 because in 4.1 everything is in UTF-8
      
      
      sql/ha_innodb.cc:
        Fix for the 0xA0 character problem in the InnoDB FOREIGN KEY parser: if my_isspace() treats 0xA0 as space, then let InnoDB do the same; this might break some multi-byte charset id's, though for big5, ujis, sjis this seems not to change the current behavior (I checked the tables in /share/charsets); this fix must NOT be merged to 4.1 because in 4.1 everything is in UTF-8
      innobase/dict/dict0dict.c:
        Fix for the 0xA0 character problem in the InnoDB FOREIGN KEY parser: if my_isspace() treats 0xA0 as space, then let InnoDB do the same; this might break some multi-byte charset id's, though for big5, ujis, sjis this seems not to change the current behavior (I checked the tables in /share/charsets); this fix must NOT be merged to 4.1 because in 4.1 everything is in UTF-8
      innobase/include/dict0dict.h:
        Fix for the 0xA0 character problem in the InnoDB FOREIGN KEY parser: if my_isspace() treats 0xA0 as space, then let InnoDB do the same; this might break some multi-byte charset id's, though for big5, ujis, sjis this seems not to change the current behavior (I checked the tables in /share/charsets); this fix must NOT be merged to 4.1 because in 4.1 everything is in UTF-8
      c486461e