1. 20 Jun, 2003 1 commit
    • hf@deer.(none)'s avatar
      Proposed fix for #615 · eb901ea4
      hf@deer.(none) authored
      So now for the CREATE TABLE foo (id integer NOT NULL default 9)
      INSERT INTO foo VALUES (NULL); we get an error
      INSERT INTO foo VALUES (1), (NULL), (2); we get one warning
                and second record is set to 9
      
      Is that what we want?
      eb901ea4
  2. 19 Jun, 2003 2 commits
  3. 18 Jun, 2003 6 commits
  4. 17 Jun, 2003 4 commits
  5. 16 Jun, 2003 4 commits
  6. 15 Jun, 2003 4 commits
  7. 14 Jun, 2003 4 commits
  8. 13 Jun, 2003 1 commit
  9. 12 Jun, 2003 8 commits
  10. 11 Jun, 2003 4 commits
  11. 10 Jun, 2003 2 commits
    • guilhem@mysql.com's avatar
      Merge gbichot@213.136.52.20:/home/bk/mysql-4.0 · 27c70dc8
      guilhem@mysql.com authored
      into mysql.com:/home/mysql_src/mysql-4.0
      27c70dc8
    • guilhem@mysql.com's avatar
      More error messages. This is intended to help debugging; presently I have a · 96c8d91a
      guilhem@mysql.com authored
      support issue with an unclear message which can have N reasons for appearing.
      This should help us know at which point it failed, and get the errno when
      my_open was involved (as the reason for the unclear message is often a
      permission problem).
      RESET SLAVE resets last_error and last_errno in SHOW SLAVE STATUS (without this,
      rpl_loaddata.test, which is expected to generate an error in last_error, influenced
      rpl_log_pos.test).
      A small test update.
      Added STOP SLAVE to mysql-test-run to get rid of several stupid error messages
      which are printed while the master restarts and the slave attempts/manages to
      connect to it and sends it nonsense binlog requests.
      96c8d91a