An error occurred fetching the project authors.
  1. 28 Apr, 2004 1 commit
  2. 07 Apr, 2004 1 commit
  3. 05 Apr, 2004 1 commit
    • monty@mysql.com's avatar
      Fixed many compiler warnings · 42cf92ce
      monty@mysql.com authored
      Fixed bugs in group_concat with ORDER BY and DISTINCT (Bugs #2695, #3381 and #3319)
      Fixed crash when doing rollback in slave and the io thread catched up with the sql thread
      Set locked_in_memory properly
      42cf92ce
  4. 04 Apr, 2004 1 commit
  5. 02 Apr, 2004 1 commit
    • dlenev@jabberwock.localdomain's avatar
      WL#1266 "Separate auto-set logic from TIMESTAMP type." · f6bff2e6
      dlenev@jabberwock.localdomain authored
      Final version of patch.
      
      Adds support for specifying of DEFAULT NOW() and/or ON UPDATE NOW()
      clauses for TIMESTAMP field definition.
      Current implementation allows only one such field per table and
      uses several unireg types for storing info about this properties of
      field. It should be replaced with better implementation when new
      .frm format is introduced.
      f6bff2e6
  6. 01 Apr, 2004 1 commit
  7. 30 Mar, 2004 1 commit
  8. 29 Mar, 2004 1 commit
  9. 26 Mar, 2004 1 commit
  10. 15 Mar, 2004 1 commit
    • vva@eagle.mysql.r18.ru's avatar
      actions for bug · 189761bc
      vva@eagle.mysql.r18.ru authored
      #2709 Affected Rows for ON DUPL. KEY undocumented, perheps illogical 
      1. added COPY_INFO::updated to work with it in
         'insert .. on duplicate' instead of COPY_INFO::deleted
      2. added affected rows to output of "info:" in mysqltest.c
      189761bc
  11. 04 Mar, 2004 2 commits
  12. 16 Feb, 2004 1 commit
  13. 10 Feb, 2004 1 commit
  14. 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
  15. 02 Feb, 2004 1 commit
  16. 01 Feb, 2004 1 commit
  17. 02 Jan, 2004 1 commit
  18. 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
  19. 21 Dec, 2003 1 commit
  20. 19 Dec, 2003 1 commit
  21. 17 Dec, 2003 1 commit
  22. 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
  23. 10 Dec, 2003 1 commit
  24. 04 Dec, 2003 1 commit
  25. 20 Nov, 2003 1 commit
  26. 15 Oct, 2003 1 commit
  27. 11 Oct, 2003 1 commit
  28. 08 Oct, 2003 2 commits
  29. 06 Oct, 2003 2 commits
  30. 26 Sep, 2003 1 commit
    • hf@deer.(none)'s avatar
      SCRUM: · ba8fa76f
      hf@deer.(none) authored
      WL#604 Privileges in embedded library
      code added to check privileges in embedded library
      NO_EMBEDDED_ACCESS_CHECKS macros inserted in code so we can exclude
      access-checking parts. Actually we now can exclude these parts from
      standalone server as well. Do we need it?
      Access checks are disabled in embedded server by default. One should
      edit libmysqld/Makefile manually to get this working.
      We definitely need the separate configure for embedded server
      ba8fa76f
  31. 24 Sep, 2003 1 commit
  32. 13 Sep, 2003 1 commit
  33. 22 Aug, 2003 2 commits
    • serg@serg.mylan's avatar
      bug #1078. two innodb+delayed crashes · eb3912c0
      serg@serg.mylan authored
      eb3912c0
    • 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
  34. 28 Jul, 2003 1 commit
  35. 22 Jul, 2003 1 commit
  36. 21 Jul, 2003 1 commit