An error occurred fetching the project authors.
  1. 24 Nov, 2005 1 commit
    • evgen@moonbone.local's avatar
      Fix bug #14482 Wrongly applied optimization in resolve_const_item() caused · a4a3215a
      evgen@moonbone.local authored
      crash
      
      resolve_const_item() substitutes item which will evaluate to constant with
      equvalent constant item, basing on the item's result type. In this case
      subselect was resolved as constant, and resolve_const_item() was substituting
      it's result's Item_caches to Item_null. Later Item_cache's function was called
      for Item_null object, which caused server crash.
      
      resolve_const_item() now substitutes constants for items with 
      result_type == ROW_RESULT only for Item_rows.
      a4a3215a
  2. 13 Oct, 2005 3 commits
  3. 12 Oct, 2005 1 commit
  4. 09 Oct, 2005 1 commit
    • evgen@moonbone.local's avatar
      Fix bug#7672 Unknown column error in order clause · 6bfc2d4b
      evgen@moonbone.local authored
      When fixing Item_func_plus in ORDER BY clause field c is searched in all
      opened tables, but because c is an alias it wasn't found there.
      
      This patch adds a flag to select_lex which allows Item_field::fix_fields() 
      to look up in select's item_list to find aliased fields.
      6bfc2d4b
  5. 07 Oct, 2005 1 commit
  6. 03 Oct, 2005 1 commit
  7. 27 Sep, 2005 1 commit
    • evgen@moonbone.local's avatar
      Fix bug#13356 resolve_const_item() wasn't able to handle Item_row items. · 4f4711bd
      evgen@moonbone.local authored
      resolve_const_item() assumed to be not called for Item_row items. For
      ensuring that DBUG_ASSERT(0) was set there.
      
      This patch adds section for Item_row items. If it can it recursively calls
      resolve_const_item() for each item the Item_row contains. If any of the
      contained items is null then whole Item_row substitued by Item_null. Otherwise
      it just returns.
      4f4711bd
  8. 28 Jul, 2005 1 commit
  9. 19 Jul, 2005 1 commit
  10. 17 Jul, 2005 1 commit
    • igor@rurik.mysql.com's avatar
      select.result, select.test: · 54dd7e5e
      igor@rurik.mysql.com authored
        Added a test case for bug #11745.
      sql_select.cc:
        Fixed bug # 11745.
        Added support of where clause for queries with FROM DUAL.
      sql_yacc.yy:
        Fixed bug # 11745.
        Added optional where clause for queries with FROM DUAL.
      54dd7e5e
  11. 16 Jul, 2005 1 commit
    • timour@mysql.com's avatar
      Added test for Bug #11521 · ff0c7f22
      timour@mysql.com authored
      "Negative integer keys incorrectly substituted for 0 during range analysis."
      
      The problem is that the range optimizer incorrectly replaces any negative
      constant with '0' for all types except BIGINT because the method save_in_field()
      casts negative integers to non-negative. This causes incorrect query
      results where (0 = any_negative_number).
      
      The problem caused by this bug is fixed by the patch for BUG#11185.
      That patch constitutes an optimization due to which the problem code is
      never called with negative constants. This patch adds a test so we are sure
      that the problem does not reappear.
      ff0c7f22
  12. 15 Jul, 2005 1 commit
    • evgen@moonbone.local's avatar
      Fix bug#11482 4.1.12 produces different resultset for a complex query · 0298bc34
      evgen@moonbone.local authored
        than in previous 4.1.x
      
      Wrongly applied optimization were adding NOT NULL constraint which results in
      rejecting valid rows and reduced result set.
      
      The problem was that add_notnull_conds() while checking subquery were adding
      NOT NULL constraint to left joined table, to which, normally, optimization 
      don't have to be applied.
      0298bc34
  13. 14 Jul, 2005 1 commit
  14. 28 Jun, 2005 1 commit
    • bell@sanja.is.com.ua's avatar
      fixed not_null_tables() for IN() (BUG#9393) · 9283e3e3
      bell@sanja.is.com.ua authored
      (IN() remove NULL rows only for tables from first argument (value which we looking for in IN() list) but not for tables from IN() list)
      Also it will be better change Item::not_null_tables() to prohibit this optimisation by default for new created items in 5.0 or 5.1.
      9283e3e3
  15. 24 May, 2005 1 commit
  16. 15 May, 2005 1 commit
    • sergefp@mysql.com's avatar
      Fix for BUG#10095: {wrong query results because of incorrect constant propagation} · f08287f3
      sergefp@mysql.com authored
      The problem: base_list::remove didn't modify base_list::last when removing 
      the last list element.
      The fix: If we remove the last element, find the element before it (by walking
      from the beginning of the list) and set base_list::last accordingly.
      
      The list gets corrupted in both 4.0 and 4.1. There are no visible problems in 
      current 4.1 because current 4.1 doesn't call where_cond->fix_fields() after 
      constant propagation step.
      f08287f3
  17. 13 May, 2005 1 commit
  18. 09 May, 2005 1 commit
  19. 31 Mar, 2005 1 commit
  20. 09 Mar, 2005 1 commit
    • timour@mysql.com's avatar
      Fix for BUG#7425. · f489e562
      timour@mysql.com authored
      The reported problems were due to two completely unrelated omissions.
      1) The file sort procedure didn't correctly create the sort key in
         make_sortkey when the sortkey was an unsigned integer.
      2) The name resolution procedure for column references inside a HAVING
         clause did not propagate the unsigned_flag of the resolved references.
      This patch corrects both problems.
      f489e562
  21. 17 Feb, 2005 1 commit
    • igor@rurik.mysql.com's avatar
      select.result, select.test: · eedde7ba
      igor@rurik.mysql.com authored
        Added a test case for bug #7098.
      sql_select.cc:
        Fixed bug #7098.
        When a string field was substituted for an equal constant
        the collation of the constant was changed by mistake for 
        the binary collation.
      eedde7ba
  22. 11 Feb, 2005 1 commit
    • igor@rurik.mysql.com's avatar
      select.result, select.test: · 8b3d59ad
      igor@rurik.mysql.com authored
        Added a test case for bug #7520.
      table.cc:
        Fixed bug #7520.
        The bug was caused by a wrong calculation of the field max_key_length for
        a TABLE structure when there was an index on a blob field.
      8b3d59ad
  23. 28 Nov, 2004 1 commit
  24. 26 Nov, 2004 1 commit
  25. 16 Nov, 2004 1 commit
  26. 26 Oct, 2004 1 commit
    • monty@mysql.com's avatar
      A lot of fixes for prepared statements (PS): · 6fbc869d
      monty@mysql.com authored
      New mysqltest that can run mysqltest with PS
      Added support for ZEROFILL in PS
      Fixed crash when one called mysql_stmt_store_result() without a preceding mysql_stmt_bind_result()
      Updated test cases to support --ps-protocol
      (Some tests are still run using old protocol)
      Fixed crash in PS when using SELECT * FROM t1 NATURAL JOIN t2...
      Fixed crash in PS when using sub queries
      Create table didn't signal when table was created. This could cause a "DROP TABLE created_table" in another thread to wait "forever"
      Fixed wrong permissions check in PS and multi-table updates (one could get permission denied for legal quries)
      Fix for PS and SELECT ... PROCEDURE
      Reset all warnings when executing a new PS query
      group_concat(...ORDER BY) didn't work with PS
      Fixed problem with test suite when not using innodb
      6fbc869d
  27. 07 Oct, 2004 1 commit
    • monty@mysql.com's avatar
      After merge fixes · 6239edc1
      monty@mysql.com authored
      Some bigger code changes was necessary becasue of the multi-table-update and the new HANDLER code
      6239edc1
  28. 07 Sep, 2004 2 commits
  29. 03 Sep, 2004 1 commit
    • igor@rurik.mysql.com's avatar
      select.result, select.test: · f888026f
      igor@rurik.mysql.com authored
        Added a test case for bug #5333.
      null_key.result, key_primary.result:
        Made covering index usable for const tables.
      sql_select.cc:
        Made covering index usable for const tables:
        downported the corresponding code from 4.1.
        Simultaneously fixed bug #5333 reported for 4.1.
        The bug was due to the fact that field index in join
        structures was always set to 0 for const tables.
      f888026f
  30. 30 Aug, 2004 1 commit
  31. 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
  32. 22 Jan, 2004 1 commit
  33. 10 Dec, 2003 1 commit
  34. 30 Oct, 2003 1 commit
  35. 16 Sep, 2003 1 commit
  36. 25 Jul, 2003 1 commit
  37. 26 Jun, 2003 1 commit