An error occurred fetching the project authors.
  1. 08 May, 2007 1 commit
  2. 19 Oct, 2006 1 commit
  3. 26 Jan, 2006 1 commit
  4. 24 Jan, 2006 1 commit
  5. 01 Sep, 2005 1 commit
  6. 31 Aug, 2005 1 commit
  7. 28 Jul, 2005 1 commit
  8. 25 Mar, 2005 1 commit
    • gbichot@quadita2.mysql.com's avatar
      WWe now store the catalog in Query_log_event in binlog WITHOUT its end zero. · ead47f47
      gbichot@quadita2.mysql.com authored
      This saves one byte per Query_log_event on disk compared to 5.0.[0..3]. Compatibility problems with 5.0.x where x<4
      are explained in the comments in log_event.cc. Putting back s/my_open(O_TRUNC)/(my_delete+my_create) change which had
      been wiped away by somebody doing a wrong 4.1->5.0 merge (which happened just
      before 5.0.3 :( ). Applying it to new events for LOAD DATA INFILE.
      If slave fails in Execute_load_query_log_event::exec_event(),
      don't delete the file (so that it's re-usable at next START SLAVE).
      And (youpi!) fix for BUG#3247 "a partially completed LOAD DATA INFILE is not
      executed at all on the slave" (storing an Execute_load_query_log_event
      to binlog, with its error code, instead of Delete_file_log_event).
      ead47f47
  9. 16 Mar, 2005 1 commit
    • dlenev@brandersnatch.localdomain's avatar
      WL#874 "Extended LOAD DATA". · f1691140
      dlenev@brandersnatch.localdomain authored
      Now one can use user variables as target for data loaded from file
      (besides table's columns). Also LOAD DATA got new SET-clause in which
      one can specify values for table columns as expressions.
      
      For example the following is possible:
      LOAD DATA INFILE 'words.dat' INTO TABLE t1 (a, @b) SET c = @b + 1;
      
      This patch also implements new way of replicating LOAD DATA.
      Now we do it similarly to other queries.
      We store LOAD DATA query in new Execute_load_query event
      (which is last in the sequence of events representing LOAD DATA).
      When we are executing this event we simply rewrite part of query which
      holds name of file (we use name of temporary file) and then execute it
      as usual query. In the beggining of this sequence we use Begin_load_query
      event which is almost identical to Append_file event
      f1691140
  10. 19 Dec, 2003 1 commit
    • guilhem@gbichot2's avatar
      This is the final commit for Worklog tasks: · df3b1a54
      guilhem@gbichot2 authored
         * A more dynamic binlog format which allows small changes (1064)
         * Log session variables in Query_log_event (1063)
      It contains a few bugfixes (which I made when running the testsuite).
      I carefully updated the results of the testsuite (i.e. I checked for every one,
      if the difference between .reject and .result could be explained).
      Apparently mysql-test-run --manager is broken in 4.1 and 5.0 currently,
      so I could neither run the few tests which require --manager, nor check
      that they pass nor modify their .result. But for builds, we don't run
      with --manager.
      Apart from --manager, the full testsuite passes, with Valgrind too (no errors).
      I'm going to push in the next minutes. Remains: update the manual.
      Note: by chance I saw that (in 4.1, in 5.0) rpl_get_lock fails when run alone;
      this is normal at it makes assumptions on thread ids. I will fix this one day
      in 4.1.
      df3b1a54
  11. 09 Oct, 2003 1 commit
  12. 08 Oct, 2003 1 commit
    • guilhem@gbichot2's avatar
      Final push for WL#1098: · c0075fa6
      guilhem@gbichot2 authored
      "Add a column "Timestamp_of_last_master_event_executed" in SHOW SLAVE STATUS".
      Finally this is adding
      - Slave_IO_State (a copy of the State column of SHOW PROCESSLIST for the I/O thread,
      so that the users, most of the time, has enough info with only SHOW SLAVE STATUS).
      - Seconds_behind_master. When the slave connects to the master it does SELECT UNIX_TIMESTAMP()
      on the master, computes the absolute difference between the master's and the slave's clock.
      It records the timestamp of the last event executed by the SQL thread, and does a
      small computation to find the number of seconds by which the slave is late.
      c0075fa6
  13. 24 Sep, 2003 1 commit
    • guilhem@mysql.com's avatar
      Fix for BUG#1391: · 9854acae
      guilhem@mysql.com authored
      "If LOAD DATA INFILE 'small_file' fails on master, slave leaves temp files"
      (the bug is in the master)
      9854acae
  14. 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
  15. 20 Aug, 2003 1 commit
    • guilhem@mysql.com's avatar
      First commit for fixing BUG#1100 · 1dd53ed0
      guilhem@mysql.com authored
      "LOAD DATA INFILE is badly filtered by binlog-*-db rules".
      There will probably be a second final one to merge Dmitri's changes
      to rpl_log.result and mine.
      2 new tests:
      rpl_loaddata_rule_m : test of logging of LOAD DATA INFILE when the master has binlog-*-db rules,
      rpl_loaddata_rule_s : test of logging of LOAD DATA INFILE when the slave has binlog-*-db rules and --log-slave-updates.
      1dd53ed0
  16. 04 Aug, 2003 1 commit
    • guilhem@mysql.com's avatar
      2 bugfixes: · bb12d905
      guilhem@mysql.com authored
      - Bug #985: "Between RESET SLAVE and START SLAVE, SHOW SLAVE STATUS is wrong."
      Now RESET SLAVE puts correct info in mi->host etc. A new test rpl_reset_slave
      for that.
      - Bug #986: "CHANGE MASTER & START SLAVE do not reset error columns in SHOW
      SLAVE STATUS". Now these reset the errors.
      bb12d905
  17. 23 Jul, 2003 1 commit
  18. 16 Jun, 2003 1 commit
  19. 03 Jun, 2003 1 commit
    • guilhem@mysql.com's avatar
      -- Waiting for Monty's approval before push -- · 3b974039
      guilhem@mysql.com authored
      Bug 571: play LOAD DATA INFILE the same way on the slave as it was on the master: 
      if it was with IGNORE, do it with IGNORE,
      if it was with REPLACE, do it with REPLACE,
      and (the change) if it was with nothing, do it with nothing (not with IGNORE !!).
      Bug 573: print a proper error message in case of duplicate entry in LOAD DATA INFILE
      on the slave, i.e. a message where the keyname and key value appear :
      'Duplicate entry '1' for key 1' and not 'Duplicate entry '%-.64s' for key %d'
      3b974039
  20. 21 May, 2003 1 commit
  21. 20 May, 2003 1 commit
  22. 03 Apr, 2003 1 commit
  23. 14 Jan, 2003 1 commit