1. 16 May, 2007 3 commits
    • 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
    • msvensson@pilot.blaudden's avatar
      Merge bk-internal:/home/bk/mysql-5.0-maint · 19618b53
      msvensson@pilot.blaudden authored
      into  pilot.blaudden:/home/msvensson/mysql/mysql-5.0-maint
      19618b53
    • msvensson@pilot.blaudden's avatar
      Fix for bug #28240: "isinf()" cannot be used in C++ for lack of prototype · 47d3829f
      msvensson@pilot.blaudden authored
      - Since isinf() portability across various platforms and
        compilers is a complicated question, we should not use
        it directly. Instead, the my_isinf() macro should be used,
        which is defined as an alias to the system-defined isinf()
        if it is safe to use, or a workaround implementation otherwise
      47d3829f
  2. 15 May, 2007 4 commits
  3. 10 May, 2007 2 commits
  4. 09 May, 2007 6 commits
  5. 07 May, 2007 4 commits
  6. 04 May, 2007 4 commits
  7. 02 May, 2007 3 commits
  8. 01 May, 2007 2 commits
  9. 30 Apr, 2007 10 commits
  10. 29 Apr, 2007 2 commits
    • igor@olga.mysql.com's avatar
      Fixed bug #24856: the result set of a ROLLUP query with DISTINCT could lack · ce0be732
      igor@olga.mysql.com authored
      some rollup rows (rows with NULLs for grouping attributes) if GROUP BY
      list contained constant expressions.
      
      This happened because the results of constant expressions were not put
      in the temporary table used for duplicate elimination. In fact a constant
      item from the GROUP BY list of a ROLLUP query can be replaced for an
      Item_null_result object when a rollup row is produced . 
      
      Now the JOIN::rollup_init function wraps any constant item referenced in
      the GROYP BY list of a ROLLUP query into an Item_func object of a special
      class that is never detected as constant item. This ensures creation of
      fields for such  constant items in temporary tables and guarantees right
      results when the result of the rollup operation first has to be written
      into a temporary table, e.g. in the cases when duplicate elimination is
      required.  
      ce0be732
    • evgen@moonbone.local's avatar
      Merge epotemkin@bk-internal.mysql.com:/home/bk/mysql-5.0-opt · 7505fc82
      evgen@moonbone.local authored
      into  moonbone.local:/mnt/gentoo64/work/16377-bug-5.0-opt-mysql
      7505fc82