1. 04 Dec, 2003 2 commits
  2. 03 Dec, 2003 3 commits
  3. 02 Dec, 2003 6 commits
    • unknown's avatar
      Merge gbichot@bk-internal.mysql.com:/home/bk/mysql-4.0 · e8fc6d46
      unknown authored
      into mysql.com:/home/mysql_src/mysql-4.0
      
      
      e8fc6d46
    • unknown's avatar
      Merge spetrunia@bk-internal.mysql.com:/home/bk/mysql-4.0 · 25be07f0
      unknown authored
      into mysql.com:/home/psergey/mysql-4.0
      
      
      25be07f0
    • unknown's avatar
      Fix for bug #1980 · 8be4234f
      unknown authored
      
      BitKeeper/etc/logging_ok:
        Logging to logging@openlogging.org accepted
      8be4234f
    • unknown's avatar
      Merge bk-internal.mysql.com:/home/bk/mysql-4.0 · 465881c2
      unknown authored
      into mysql.com:/home/dlenev/src/mysql-4.0-tsbg
      
      
      465881c2
    • unknown's avatar
      Fix for Bug #1448 "Date parsing fails, and fails to complain · f5d72297
      unknown authored
      about it". Now numbers representing illegal timestamps are 
      converted to 0 value if they are stored as timestamp or 
      datetime. This behaviour is consistent with manual and with 
      behaviour of string -> timestamp conversion.
      
      
      mysql-test/r/type_datetime.result:
        Added test if ranges are checked during 
        integer, string -> timestamp conversion
      mysql-test/r/type_timestamp.result:
        Added test if ranges are checked during 
        integer, string -> datetime conversion
      mysql-test/t/type_datetime.test:
        Added test if ranges are checked during 
        integer, string -> datetime conversion
      mysql-test/t/type_timestamp.test:
        Added test if ranges are checked during 
        integer, string -> timestamp conversion
      sql/field.cc:
        Checks of month, day, hour, minute and second ranges were added
        to storing of integer into Field_datetime and Field_timestamp
        and so for integer -> datetime, timestamp conversion.
      f5d72297
    • unknown's avatar
      There is no reason that Intvar_log_event's constructor calls Log_event::Log_event() · b9418600
      unknown authored
      instead of Log_event::Log_event(THD*, ...) when the event is built in the master
      to be written in the binlog.
      Rand_log_event already used the good constructor, so there really is no reason
      for Intvar_log_event to be an exception.
      This fixes a test failure of last night (which appeared after I removed a useless
      e.server_id=thd->server_id in log.cc; in fact this line was not useless because
      it hid the bad constructor).
      Replication tests pass, with Valgrind too.
      
      
      sql/log_event.h:
        There is no reason that Intvar_log_event's constructor calls Log_event::Log_event()
        instead of Log_event::Log_event(THD*, ...) when the event is built in the master
        to be written in the binlog.
        Rand_log_event already used the good constructor, so there really is no reason
        for Intvar_log_event to be an exception.
        This fixes a test failure of last night (which appeared after I removed a useless
        e.server_id=thd->server_id in log.cc; in fact this line was not useless because
        it hid the bad constructor).
      b9418600
  4. 01 Dec, 2003 2 commits
  5. 28 Nov, 2003 7 commits
  6. 27 Nov, 2003 3 commits
  7. 26 Nov, 2003 2 commits
  8. 25 Nov, 2003 3 commits
  9. 24 Nov, 2003 4 commits
  10. 23 Nov, 2003 1 commit
  11. 21 Nov, 2003 1 commit
  12. 20 Nov, 2003 6 commits