1. 10 Dec, 2003 13 commits
  2. 09 Dec, 2003 16 commits
  3. 08 Dec, 2003 3 commits
    • unknown's avatar
      Create PID file with O_TRUNC, so that it is emptied before it is written to. · 9a1cb59c
      unknown authored
      Otherwise, if the previous run ended with a crash, and the PID was 1234,
      and you have rebooted the machine and the new PID is 99 then in the PID
      file you will have 9934.
      Note: users of mysqld_safe did not have the problem because this script
      deletes the PID file before starting mysqld.
      
      
      9a1cb59c
    • unknown's avatar
      Merge gbichot@bk-internal.mysql.com:/home/bk/mysql-4.0 · c121a735
      unknown authored
      into mysql.com:/home/mysql_src/mysql-4.0
      
      
      c121a735
    • unknown's avatar
      Fix for BUG#2045 "Sending SIGHUP to mysqld crashes it if running with --log-bin". · a50761a5
      unknown authored
      The constructor of Rotate_log_event used when we are rotating our binlog or
      relay log, should not assume that there is a nonzero THD available.
      For example, when we are reacting to SIGHUP, the THD is 0.
      In fact we don't need to use the THD in this constructor;
      we can do like for Stop_log_event, and use the minimal Log_event
      constructor.
      If we were allowed to put Unix-specific commands in the testsuite,
      I'd add a test for this (<sigh>).
      
      
      sql/log.cc:
        A comment to warn that thd can be 0.
        The part about LOG_EVENT_FORCED_ROTATE_F is just to avoid segfault;
        this flag is already removed in 4.1 anyway.
      sql/log_event.cc:
        A comment.
      sql/log_event.h:
        The constructor of Rotate_log_event used when we are rotating our binlog or
        relay log, should not assume that there is a nonzero THD available.
        For example, when we are reacting to SIGHUP, the THD is 0.
        In fact we don't need to use the THD in this constructor;
        we can do like for Stop_log_event, and use the minimal Log_event
        constructor.
        This fixes BUG#2045 
        "Sending SIGHUP to mysqld crashes it if running with --log-bin"
      a50761a5
  4. 07 Dec, 2003 3 commits
    • unknown's avatar
      Merge sgluhov@bk-internal.mysql.com:/home/bk/mysql-4.0 · da3e63e1
      unknown authored
      into gluh.mysql.r18.ru:/home/gluh/mysql-4.0.defweek
      
      
      sql/mysqld.cc:
        Auto merged
      da3e63e1
    • unknown's avatar
      WL#1175: more default_week_formats for iso compatibility · 468dcb60
      unknown authored
      New formats added for 'week()' function and 'default_week_format' option(4 - 7).
      Next formats is supported now:
      *Value* *Meaning*
        `0'     Week starts on Sunday; First Sunday of the year starts week 1.
        	  Week() returns 0-53.
        `1'     Week starts on Monday; Weeks numbered according to ISO 8601:1988.
      	  Week() returns 0-53.
        `2'     Week starts on Sunday; First Sunday of the year starts week 1.
        	  Week() returns 1-53.
        `3'     Week starts on Monday; Weeks numbered according to ISO 8601:1988.
      	  Week() returns 1-53.
        `4'     Week starts on Sunday; Weeks numbered according to ISO 8601:1988.
      	  Week() returns 0-53.
        `5'     Week starts on Monday;  First Monday of the year starts week 1.
        	  Week() returns 0-53.
        `6'     Week starts on Sunday; Weeks numbered according to ISO 8601:1988.
      	  Week() returns 1-53.
        `7'     Week starts on Monday;  First Monday of the year starts week 1.
        	  Week() returns 1-53.
      
      
      mysql-test/r/func_time.result:
        Test for 'default_week_format' option and 'week' function
      mysql-test/t/func_time.test:
        Test for 'default_week_format' option and 'week' function
      sql/item_timefunc.cc:
        WL#1175 more default_week_formats for iso compatibility
      sql/mysql_priv.h:
        WL#1175 more default_week_formats for iso compatibility
      sql/mysqld.cc:
        WL#1175 more default_week_formats for iso compatibility
      sql/time.cc:
        WL#1175 more default_week_formats for iso compatibility
      468dcb60
    • unknown's avatar
      Merge sgluhov@bk-internal.mysql.com:/home/bk/mysql-4.0 · f35c834d
      unknown authored
      into gluh.mysql.r18.ru:/home/gluh/mysql-4.0.pass
      
      
      sql/sql_parse.cc:
        Auto merged
      f35c834d
  5. 05 Dec, 2003 3 commits
    • unknown's avatar
      Fix for #1890 and #1959 · 007d2e5a
      unknown authored
      This bug happens under Windows & Embedded server
      Reason is that pthread_self() always returns NULL in this case.
      This confuses thr_lock function and it doesn't stop
      thread inserting in the write-locked table.
      
      Global problem is that there's no way under Windows to get
      unique thread handle for working thread.
      Monty made a workaround for server - we store the thread's handle
      we get when we create thread in the thread-specific variable.
      This doesn't work with the embedded library for we don't control
      thread creation there.
      
      I added code that sets CurrentThreadId as the pthread_self
      for the embedded library.
      It seems to solve problem because it's unique and we don't use
      pthread_self as a parameter for thread functions in embedded library. 
      
      
      mysys/my_thr_init.c:
        setting of tmp->thread_self added
      007d2e5a
    • unknown's avatar
      typo fixed · e425b98a
      unknown authored
      e425b98a
    • unknown's avatar
      attempt to make ULONGLONG_MAX work on Windows. · d4e3cc72
      unknown authored
      
      include/config-win.h:
        ULONGLONG_MAX definition added
      include/my_global.h:
        comment about config-win.h added
      d4e3cc72
  6. 04 Dec, 2003 2 commits