1. 26 Jan, 2005 1 commit
  2. 25 Jan, 2005 2 commits
    • unknown's avatar
      order_by.result, order_by.test: · 657b2c96
      unknown authored
        Added a test case for bug #7672.
      sql_yacc.yy:
        Fixed bug #7672.
        Made queries of the form (SELECT ...) ORDER BY ... to
        be equivalent to SELECT ... ORDER BY ...
      
      
      sql/sql_yacc.yy:
        Fixed bug #7672.
        Made queries of the form (SELECT ...) ORDER BY ... to
        be equivalent to SELECT ... ORDER BY ...
      mysql-test/t/order_by.test:
        Added a test case for bug #7672.
      mysql-test/r/order_by.result:
        Added a test case for bug #7672.
      657b2c96
    • unknown's avatar
      InnoDB: Enable ut_ad() assertions in MySQL debug builds. · 5c329477
      unknown authored
      
      innobase/include/univ.i:
        InnoDB: Define UNIV_DEBUG when DBUG_ON (in MySQL) is defined.
        This enables InnoDB debug assertions in debug builds of mysqld.
      5c329477
  3. 24 Jan, 2005 1 commit
  4. 22 Jan, 2005 1 commit
    • unknown's avatar
      select_found.result, select_found.test: · 2afeecfc
      unknown authored
        Added a test case for bug #7945.
      sql_select.cc:
        Fixed bug #7945. If DISTINCT is used only with constants
        in a query with GROUP BY, we can apply an optimization
        that set LIMIT to 1 only in the case when there is 
        no SQL_CALC_FOUND_ROWS.
      
      
      sql/sql_select.cc:
        Fixed bug #7945. If DISTINCT is used only with constants
        in a query with GROUP BY, we can apply an optimization
        that set LIMIT to 1 only in the case when there is 
        no SQL_CALC_FOUND_ROWS.
      mysql-test/t/select_found.test:
        Added a test case for bug #7945.
      mysql-test/r/select_found.result:
        Added a test case for bug #7945.
      2afeecfc
  5. 20 Jan, 2005 2 commits
  6. 19 Jan, 2005 1 commit
    • unknown's avatar
      BUG#6034 - Error code 124: Wrong medium type. · 6d466788
      unknown authored
      Version for 4.0. Committed for merge.
      If the result table is one of the select tables in INSERT SELECT,
      we must not disable the result tables indexes before selecting.
      mysql_execute_command() detects the match for other reasons and
      adds the flag OPTION_BUFFER_RESULT to the 'select_options'. 
      In this case the result is put into a temporary table first. 
      Hence, we can defer the preparation of the insert
      table until the result is to be used.
      
      
      mysql-test/r/insert_select.result:
        BUG#6034 - Error code 124:  Wrong medium type.
        The test results.
      mysql-test/t/insert_select.test:
        BUG#6034 - Error code 124:  Wrong medium type.
        The test case.
      sql/sql_select.cc:
        BUG#6034 - Error code 124:  Wrong medium type.
        With OPTION_BUFFER_RESULT in the 'select_options',
        defer the preparation of the insert table until the 
        result is to be used. Unfortunately, this happens
        at several places.
      6d466788
  7. 18 Jan, 2005 6 commits
  8. 17 Jan, 2005 1 commit
  9. 15 Jan, 2005 1 commit
  10. 14 Jan, 2005 1 commit
  11. 13 Jan, 2005 3 commits
    • unknown's avatar
      Fix mysql_install_db to look for libexecdir relative to basedir when · 0898b40c
      unknown authored
      it has been specified. (Bug #7347)
      
      
      scripts/mysql_install_db.sh:
        When basedir is specified, look for libexecdir relative to that
      0898b40c
    • unknown's avatar
      ha_innodb.cc: · 3a1d782e
      unknown authored
        Fix a theoretical hang over the adaptive hash latch in InnoDB if one runs INSERT ... SELECT ... (binlog not enabled), or a multi-table UPDATE or DELETE, and only the read tables are InnoDB type, the rest are MyISAM; this also fixes bug #7879 for InnoDB type tables
      
      
      sql/ha_innodb.cc:
        Fix a theoretical hang over the adaptive hash latch in InnoDB if one runs INSERT ... SELECT ... (binlog not enabled), or a multi-table UPDATE or DELETE, and only the read tables are InnoDB type, the rest are MyISAM; this also fixes bug #7879 for InnoDB type tables
      3a1d782e
    • unknown's avatar
      Merge marko@bk-internal.mysql.com:/home/bk/mysql-4.0 · 1084e141
      unknown authored
      into hundin.mysql.fi:/home/marko/k/mysql-4.0
      
      1084e141
  12. 12 Jan, 2005 6 commits
  13. 10 Jan, 2005 1 commit
  14. 07 Jan, 2005 1 commit
    • unknown's avatar
      Bootstrap: · dfeeb1a1
      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>.
      dfeeb1a1
  15. 06 Jan, 2005 2 commits
  16. 05 Jan, 2005 1 commit
    • unknown's avatar
      Allow DEFAULT_THREAD_STACK to be set via -DDEFAULT_THREAD_STACK=... so our · 717f3cac
      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=...
      717f3cac
  17. 04 Jan, 2005 1 commit
  18. 03 Jan, 2005 1 commit
  19. 31 Dec, 2004 2 commits
  20. 30 Dec, 2004 3 commits
  21. 27 Dec, 2004 2 commits
    • unknown's avatar
      row0mysql.c: · 9e893300
      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
      9e893300
    • unknown's avatar
      row0ins.c: · 5fded139
      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
      5fded139