An error occurred fetching the project authors.
  1. 31 May, 2005 1 commit
    • ingo@mysql.com's avatar
      Bug#10224 - ANALYZE TABLE crashing with simultaneous CREATE ... SELECT statement. · 51d80960
      ingo@mysql.com authored
      1.) Added a new option to mysql_lock_tables() for ignoring FLUSH TABLES.
      Used the new option in create_table_from_items().
      It is necessary to prevent the SELECT table from being reopend.
      It would get new storage assigned for its fields, while the
      SELECT part of the command would still use the old (freed) storage.
      2.) Protected the CREATE TABLE and CREATE TABLE ... SELECT commands
      against a global read lock. This prevents a deadlock in
      CREATE TABLE ... SELECT in conjunction with FLUSH TABLES WITH READ LOCK
      and avoids the creation of new tables during a global read lock.
      3.) Replaced set_protect_against_global_read_lock() and
      unset_protect_against_global_read_lock() by
      wait_if_global_read_lock() and start_waiting_global_read_lock()
      in the INSERT DELAYED handling.
      51d80960
  2. 27 Apr, 2005 1 commit
  3. 02 Dec, 2004 1 commit
    • jimw@mysql.com's avatar
      Prevent adding 'CREATE TABLE .. SELECT' query to the binary log when the · 13649d90
      jimw@mysql.com authored
      insertion of new records partially failed. It would get logged because of the
      logic to log a partially-failed 'INSERT ... SELECT' (which can't be rolled back
      in non-transactional tables), but 'CREATE TABLE ... SELECT' is always rolled
      back on failure, even for non-transactional tables. (Bug #6682)
      (Original fix reimplemented after review by Serg and Guilhem.)
      13649d90
  4. 18 Jul, 2004 1 commit
  5. 28 Apr, 2004 1 commit
  6. 04 Mar, 2004 2 commits
  7. 10 Feb, 2004 1 commit
  8. 09 Feb, 2004 1 commit
    • heikki@hundin.mysql.fi's avatar
      row0mysql.c: · d9790a40
      heikki@hundin.mysql.fi authored
        Allow always DROPping of a table which is only referenced by FOREIGN KEY constraints from the same table
      Many files:
        Do not let REPLACE to perform internally an UPDATE if the table is referenced by a FOREIGN KEY: the manual says that REPLACE must resolve a duplicate key error semantically with DELETE(s) + INSERT, and not by an UPDATE; the internal update caused foreign key checks and cascaded operations to behave in a semantically wrong way
      d9790a40
  9. 30 Dec, 2003 1 commit
    • monty@mysql.com's avatar
      Some small portability fixes. · c1dd070b
      monty@mysql.com authored
      Added support for lower_case_table_names=2, which is to be used on case insensitive file systems.
      This tells MySQL to preserve the used case of filenames and database names to make it esier to move files between cases sensitive can case insensitive file systems (like Windows and Linux)
      c1dd070b
  10. 16 Dec, 2003 1 commit
    • guilhem@mysql.com's avatar
      Fix for BUG#2083 · db2d812d
      guilhem@mysql.com authored
      "EE_ error codes (EE_DELETE, EE_WRITE) end up in the binlog, making slave stop".
      The problem was that during execution of the command on the master, an error
      can occur (for example, not space left on device, then mysqld waits and when
      there is space it completes successfully: so finally it worked but the error
      EE_WRITE remains in thd->net.last_errno and thd->net.last_error).
      To know if finally the command succeeded, we test the 'error' variable in
      every place, and if it shows no failure we reset thd->net.last_err* using
      the function THD::clear_error() which is backported from 4.1.
      A new test to see if now only real errors get to the binlog (note: the test
      uses "rm").
      
      Also a bit of memory free/alloc saving in log_event.cc (do not free the whole
      mem_root after every query in the slave SQL thread: we can keep the initial
      block of it; which will be freed when the thread terminates).
      db2d812d
  11. 10 Dec, 2003 1 commit
  12. 04 Dec, 2003 1 commit
  13. 15 Oct, 2003 1 commit
  14. 06 Oct, 2003 1 commit
  15. 22 Aug, 2003 1 commit
    • guilhem@mysql.com's avatar
      2 minor edits, plus · 759a3c1e
      guilhem@mysql.com authored
      fix for BUG#1113 "INSERT into non-trans table SELECT ; ROLLBACK" does not send warning"
      and
      fix for BUG#873 "In transaction, INSERT to non-trans table is written too early to binlog".
      Now we don't always write the non-trans update immediately to the binlog;
      if there is something in the binlog cache we write it to the binlog cache
      (because the non-trans update could depend on a trans table which was modified
      earlier in the transaction); then in case of ROLLBACK, we write the binlog
      cache to the binlog, wrapped with BEGIN/ROLLBACK.
      This guarantees that the slave does the same updates.
      For ROLLBACK TO SAVEPOINT: when we execute a SAVEPOINT command we write it
      to the binlog cache. At ROLLBACK TO SAVEPOINT, if some non-trans table was updated,
      we write ROLLBACK TO SAVEPOINT to the binlog cache; when the transaction
      terminates (COMMIT/ROLLBACK), the binlog cache will be flushed to the binlog
      (because of the non-trans update) so we'll have SAVEPOINT and ROLLBACK TO
      SAVEPOINT in the binlog.
      
      Apart from this rare case of updates of mixed table types in transaction, the
      usual way is still clear the binlog cache at ROLLBACK, or chop it at
      ROLLBACK TO SAVEPOINT (meaning the SAVEPOINT command is also chopped, which
      is fine).
      Note that BUG#873 encompasses subbugs 1) and 2) of BUG#333 "3 binlogging bugs when doing INSERT with mixed InnoDB/MyISAM".
      759a3c1e
  16. 14 Jul, 2003 1 commit
  17. 11 Jul, 2003 1 commit
    • guilhem@mysql.com's avatar
      Fix for BUG#791: · fbebac9a
      guilhem@mysql.com authored
      a safer way of initing the mutexes in MYSQL_LOG.
      is_open() is now always thread-safe.
      See each file for details.
      fbebac9a
  18. 24 May, 2003 1 commit
  19. 13 May, 2003 1 commit
  20. 27 Apr, 2003 1 commit
  21. 26 Apr, 2003 2 commits
  22. 16 Mar, 2003 1 commit
  23. 12 Mar, 2003 1 commit
  24. 09 Mar, 2003 1 commit
  25. 06 Mar, 2003 2 commits
  26. 27 Feb, 2003 1 commit
  27. 28 Jan, 2003 1 commit
    • monty@mashka.mysql.fi's avatar
      Fixes for Netware · 689578a0
      monty@mashka.mysql.fi authored
      Call pthread_mutex_destroy() on not used mutex.
      Changed comments in .h and .c files from // -> /* */
      Added detection of mutex on which one didn't call pthread_mutex_destroy()
      Fixed bug in create_tmp_field() which causes a memory overrun in queries that uses "ORDER BY constant_expression"
      Added optimisation for ORDER BY NULL
      689578a0
  28. 14 Dec, 2002 1 commit
  29. 07 Dec, 2002 1 commit
  30. 29 Nov, 2002 1 commit
    • monty@mashka.mysql.fi's avatar
      New multi-table-update code · 6603d752
      monty@mashka.mysql.fi authored
      New (simpler) internal timestamp handling.
      More debuging to heap tables.
      Small cleanups to multi-table-delete
      false -> 0 and true -> 1  (We should use TRUE and FALSE)
      6603d752
  31. 21 Nov, 2002 1 commit
  32. 20 Nov, 2002 1 commit
  33. 16 Nov, 2002 1 commit
    • monty@mashka.mysql.fi's avatar
      Small improvement to alloc_root · 1a96948e
      monty@mashka.mysql.fi authored
      Add support for LIMIT # OFFSET #
      Changed lock handling:  Now all locks should be stored in TABLE_LIST instead of passed to functions.
      Don't call query_cache_invalidate() twice in some cases
      mysql_change_user() now clears states to be equal to close + connect.
      Fixed a bug with multi-table-update and multi-table-delete when used with LOCK TABLES
      Fixed a bug with replicate-do and UPDATE
      1a96948e
  34. 07 Nov, 2002 4 commits