An error occurred fetching the project authors.
  1. 21 Jun, 2004 2 commits
  2. 18 Jun, 2004 1 commit
    • dlenev@brandersnatch.localdomain's avatar
      WL#1264 "Per-thread time zone support infrastructure". · 09ba29e5
      dlenev@brandersnatch.localdomain authored
      Added basic per-thread time zone functionality (based on public
      domain elsie-code). Now user can select current time zone
      (from the list of time zones described in system tables).
      All NOW-like functions honor this time zone, values of TIMESTAMP
      type are interpreted as values in this time zone, so now
      our TIMESTAMP type behaves similar to Oracle's TIMESTAMP WITH
      LOCAL TIME ZONE (or proper PostgresSQL type).
        
      WL#1266 "CONVERT_TZ() - basic time with time zone conversion 
      function".
        
      Fixed problems described in Bug #2336 (Different number of warnings 
      when inserting bad datetime as string or as number). This required
      reworking of datetime realted warning hadling (they now generated 
      at Field object level not in conversion functions).
        
      Optimization: Now Field class descendants use table->in_use member
      instead of current_thd macro.
      09ba29e5
  3. 13 May, 2004 1 commit
  4. 28 Apr, 2004 1 commit
    • monty@mysql.com's avatar
      Fixed http address in some scripts (Bug #3460) · f10d098f
      monty@mysql.com authored
      Output TIMESTAMP in 4.1 format for 4.1 tables (or for TIMESTAMP(19)) (portability fix)
      Fixed that INTERVAL can handle big integers. (Bug #3498)
      Fixed that hostname="" works identical as hostname="%" for table/column grants (Bug #3473)
      f10d098f
  5. 25 Mar, 2004 1 commit
  6. 23 Mar, 2004 1 commit
  7. 15 Mar, 2004 1 commit
  8. 19 Dec, 2003 1 commit
    • monty@mysql.com's avatar
      Fixes after merge with 4.0 · 031390a9
      monty@mysql.com authored
      Cleaned up embedded library access and query cache handling
      Changed min stack size to 128K (to allow longer MyISAM keys)
      Fixed wrong priority for XOR (should be less than NEG to get -1^1 to work)
      031390a9
  9. 12 Dec, 2003 1 commit
    • monty@mysql.com's avatar
      Fix autoincrement for signed columns (Bug #1366) · f995a5f4
      monty@mysql.com authored
      Fixed problem with char > 128 in QUOTE() function. (Bug #1868)
      Disable creation of symlinks if my_disable_symlink is set
      Fixed searching of TEXT with end space. (Bug #1651)
      Fixed caching bug in multi-table-update where same table was used twice. (Bug #1711)
      Fixed problem with UNIX_TIMESTAMP() for timestamps close to 0. (Bug #1998)
      Fixed timestamp.test
      f995a5f4
  10. 10 Dec, 2003 1 commit
  11. 07 Dec, 2003 1 commit
    • gluh@gluh.mysql.r18.ru's avatar
      WL#1175: more default_week_formats for iso compatibility · 48317785
      gluh@gluh.mysql.r18.ru 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.
      48317785
  12. 17 Nov, 2003 1 commit
  13. 30 Oct, 2003 1 commit
  14. 11 Aug, 2003 1 commit
  15. 19 Jun, 2003 1 commit
  16. 11 Jun, 2003 1 commit
  17. 19 Feb, 2003 1 commit
  18. 14 Dec, 2002 1 commit
    • monty@mashka.mysql.fi's avatar
      Fixes for binary protocol (complement to last push) · d49167ba
      monty@mashka.mysql.fi authored
      Changed timestamp to return string in YYYY-MM-DD HH:MM:SS format.
      DATE_ADD() and related functions now returns correct DATE/DATETIME type depending on argument types.
      Now all tests passes, still some work left to remove warnings in log files from mysql-test-run
      d49167ba
  19. 24 Nov, 2002 1 commit
  20. 22 Nov, 2002 1 commit
  21. 12 Nov, 2002 1 commit
  22. 06 Nov, 2002 1 commit
  23. 05 Nov, 2002 1 commit
  24. 04 Nov, 2001 2 commits
  25. 03 Nov, 2001 1 commit
  26. 31 Oct, 2001 1 commit
    • monty@hundin.mysql.fi's avatar
      Portability fixes · d89690e6
      monty@hundin.mysql.fi authored
      Fix for consistent 0000-00-00 date handling
      Close + open binary logs on flush tables
      Fix for AVG() in HAVING.
      d89690e6
  27. 28 Sep, 2001 1 commit
    • sasha@mysql.sashanet.com's avatar
      client/mysqlmanagerc.c · bb66c80a
      sasha@mysql.sashanet.com authored
          added support for quiet
          increased line buffer size
      client/mysqltest.c
          fixed memory leak
          added query logging to result file
          added error message logging to result file
          added enable_query_log/disable_query_log
      mysql-test/mysql-test-run.sh
          converted tests to use mysqlmanager
      
      Updated test results
      bb66c80a
  28. 21 Aug, 2001 1 commit
  29. 16 Aug, 2001 1 commit
    • sasha@mysql.sashanet.com's avatar
      fixed bug in Item_func_div::val_int() that broke all functions that · 8ca3b53a
      sasha@mysql.sashanet.com authored
      do val_int() on their arguments before starting the computation. 
      Similar fixes are need for +-* and probably several other but I want
      to make sure Monty is fine with my fix approach before changing a lot
      of code. 
      
      Amazingly,
      this bug is not as critical as you would expect since very few functions do val_int()
      on their arguments ( from_unixtime(), sec_to_time()), and those not
      very frequently perform a computation on their floating point arguments.
      which is probably why no one has yet reported this bug. Another 
      possibility is that the result is usually wrong by no more than 5%,
      which makes it hard to catch it. I found it when trying to compute mile
      splits for 30:47 10K - it told me 5:07, and I knew it was wrong because
      5:00 mile gives you 31:08. However, if I had not run as many 10K races,
      I would have easily believed that 30:47 10K is a 5:07 mile pace and 
      would not have noticed the bug.
      8ca3b53a
  30. 22 May, 2001 1 commit
  31. 09 Apr, 2001 1 commit
  32. 31 Jan, 2001 1 commit
    • monty@donna.mysql.com's avatar
      New myisamchk option --sort-recover · bdbc0ef7
      monty@donna.mysql.com authored
      Allow delete of crashed MyISAM tables
      Fixed bug when BLOB was first part of key
      Fixed bug when using result from CASE in GROUP BY
      Fixed core-dump bug in monthname()
      Optimized calling of check_db_name()
      bdbc0ef7
  33. 15 Jan, 2001 1 commit
  34. 28 Dec, 2000 1 commit