An error occurred fetching the project authors.
  1. 13 Oct, 2009 1 commit
    • Gleb Shchepa's avatar
      Backport of fix to bug #33629 into mysql-next-mr-bugfixing. · bc7c439e
      Gleb Shchepa authored
      Bug #33629: last_day function can return null, but has 'not null' flag set for result
      
      LAST_DAY and MAKEDATE functions are documented as
      returning NULL value, but actually they was implemented
      as returning NOT NULL typed values.
      
      That caused a confusing error "ERROR 1048 (23000): Column
      '...' cannot be null" on queries like: 
      
        SELECT 1 FROM (SELECT LAST_DAY('0')) a;
      bc7c439e
  2. 06 Feb, 2009 1 commit
    • Tatiana A. Nurnberg's avatar
      Bug#42525: TIMEDIFF function · b16ad3ba
      Tatiana A. Nurnberg authored
      In 37553 we declared longlong results for
      class Item_str_timefunc as per comments/docs,
      but didn't add a method for that. And the
      default just wasn't good enough for some
      cases.
      
      Changeset adds dedicated val_int() to class.
      b16ad3ba
  3. 26 Nov, 2008 1 commit
    • Tatiana A. Nurnberg's avatar
      Bug#37553: MySql Error Compare TimeDiff & Time · ae0c6a94
      Tatiana A. Nurnberg authored
      We pretended that TIMEDIFF() would always return positive results;
      this gave strange results in comparisons of the TIMEDIFF(low,hi)<TIME(0)
      type that rendered a negative result, but still gave false in comparison.
      We also inadvertantly dropped the sign when converting times to
      decimal.
      
      CAST(time AS DECIMAL) handles signs of the times correctly.
      TIMEDIFF() marked up as signed. Time/date comparison code switched to
      signed for clarity.
      ae0c6a94
  4. 12 Oct, 2007 1 commit
  5. 09 Oct, 2007 1 commit
  6. 16 May, 2007 1 commit
    • msvensson@pilot.blaudden's avatar
      Backport of TIME->MYSQL_TIME / Y2K fixset · a65d12a8
      msvensson@pilot.blaudden authored
         
      Made year 2000 handling more uniform
      Removed year 2000 handling out from calc_days()
      The above removes some bugs in date/datetimes with year between 0 and 200
      Now we get a note when we insert a datetime value into a date column
      For default values to CREATE, don't give errors for warning level NOTE
      Fixed some compiler failures
      Added library ws2_32 for windows compilation (needed if we want to compile with IOCP support)
      Removed duplicate typedef TIME and replaced it with MYSQL_TIME
      
      Better (more complete) fix for: Bug#21103 "DATE column not compared as DATE"
      Fixed properly Bug#18997 "DATE_ADD and DATE_SUB perform year2K autoconversion magic on 4-digit year value"
      Fixed Bug#23093 "Implicit conversion of 9912101 to date does not match cast(9912101 as date)"
       
      a65d12a8
  7. 14 May, 2007 2 commits
    • tnurnberg@blasphemy.mysql.com's avatar
      Backport of TIME->MYSQL_TIME / Y2K fixset · 034aec5d
      tnurnberg@blasphemy.mysql.com authored
      Made year 2000 handling more uniform
      Removed year 2000 handling out from calc_days()
      The above removes some bugs in date/datetimes with year between 0 and 200
      Now we get a note when we insert a datetime value into a date column
      For default values to CREATE, don't give errors for warning level NOTE
      Fixed some compiler failures
      Added library ws2_32 for windows compilation (needed if we want to compile with IOCP support)
      Removed duplicate typedef TIME and replaced it with MYSQL_TIME
      
      Better (more complete) fix for: Bug#21103 "DATE column not compared as DATE"
      Fixed properly Bug#18997 "DATE_ADD and DATE_SUB perform year2K autoconversion magic on 4-digit year value"
      Fixed Bug#23093 "Implicit conversion of 9912101 to date does not match cast(9912101 as date)"
      034aec5d
    • tnurnberg@blasphemy.mysql.com's avatar
      Backport of TIME->MYSQL_TIME / Y2K fixset · 30868bdc
      tnurnberg@blasphemy.mysql.com authored
      Made year 2000 handling more uniform
      Removed year 2000 handling out from calc_days()
      The above removes some bugs in date/datetimes with year between 0 and 200
      Now we get a note when we insert a datetime value into a date column
      For default values to CREATE, don't give errors for warning level NOTE
      Fixed some compiler failures
      Added library ws2_32 for windows compilation (needed if we want to compile with IOCP support)
      Removed duplicate typedef TIME and replaced it with MYSQL_TIME
      
      Better (more complete) fix for: Bug#21103 "DATE column not compared as DATE"
      Fixed properly Bug#18997 "DATE_ADD and DATE_SUB perform year2K autoconversion magic on 4-digit year value"
      Fixed Bug#23093 "Implicit conversion of 9912101 to date does not match cast(9912101 as date)"
      30868bdc
  8. 23 Mar, 2007 1 commit
    • monty@mysql.com/narttu.mysql.fi's avatar
      Removed not used define YY_MAGIC_BELOW · 19336036
      monty@mysql.com/narttu.mysql.fi authored
      Made year 2000 handling more uniform
      Removed year 2000 handling out from calc_days()
      The above removes some bugs in date/datetimes with year between 0 and 200
      Now we get a note when we insert a datetime value into a date column
      For default values to CREATE, don't give errors for warning level NOTE
      Fixed some compiler failures
      Added library ws2_32 for windows compilation (needed if we want to compile with IOCP support)
      Removed duplicate typedef TIME and replaced it with MYSQL_TIME
      
      Better (more complete) fix for: Bug#21103 "DATE column not compared as DATE"
      Fixed properly Bug#18997 "DATE_ADD and DATE_SUB perform year2K autoconversion magic on 4-digit year value"
      Fixed Bug#23093 "Implicit conversion of 9912101 to date does not match cast(9912101 as date)"
      19336036
  9. 26 Dec, 2006 1 commit
  10. 04 Oct, 2006 1 commit
    • kaa@polly.local's avatar
      Fixes a number of problems with time/datetime <-> string conversion functions: · 609a3cd2
      kaa@polly.local authored
      - bug #11655 "Wrong time is returning from nested selects - maximum time exists
      - input and output TIME values were not validated properly in several conversion functions
      - bug #20927 "sec_to_time treats big unsigned as signed"
      - integer overflows were not checked in several functions. As a result, input values like 2^32 or 3600*2^32 were treated as 0
      - BIGINT UNSIGNED values were treated as SIGNED in several functions
      - in cases where both input string truncation and out-of-range TIME value occur, only 'truncated incorrect time value' warning was produced
      609a3cd2
  11. 27 Jun, 2006 1 commit
  12. 02 Dec, 2005 1 commit
  13. 01 Nov, 2005 2 commits
  14. 18 Apr, 2005 1 commit
  15. 28 Mar, 2005 1 commit
  16. 15 Jan, 2005 2 commits
  17. 12 Jan, 2005 1 commit
  18. 10 Dec, 2004 1 commit
  19. 28 Sep, 2004 1 commit
    • monty@mishka.local's avatar
      Strict mode & better warnings · f2941380
      monty@mishka.local authored
      Under strict mode MySQL will generate an error message if there was any conversion when assigning data to a field.
      Added checking of date/datetime fields.
      If strict mode, give error if we have not given value to field without a default value (for INSERT)
      f2941380
  20. 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
  21. 15 Mar, 2004 1 commit
  22. 09 Mar, 2004 1 commit
  23. 08 Dec, 2003 1 commit
    • gluh@gluh.mysql.r18.ru's avatar
      WL#530&531: TIMESTAMPADD, TIMESTAMPDIFF functions · ec874924
      gluh@gluh.mysql.r18.ru authored
      Syntax for TIMESTAMPADD:
      
      TIMESTAMPADD(interval, integer_expression, datetime_expression)
      
      interval:= FRAC_SECOND | SECOND | MINUTE | HOUR | DAY | WEEK | MONTH | 
      QUARTER | YEAR
      
      Supported SQL_TSI_  prefix  (like SQL_TSI_SECOND)
      
      Syntax for TIMESTAMPDIFF:
      
      TIMESTAMPDIFF(interval, datetime_expression1, datetime_expression2)
      
      interval:= FRAC_SECOND | SECOND | MINUTE | HOUR | DAY | WEEK | MONTH | 
      QUARTER | YEAR
      
      Supported SQL_TSI_  prefix  (like SQL_TSI_SECOND)
      ec874924
  24. 08 Jul, 2003 1 commit
  25. 23 Jun, 2003 1 commit