An error occurred fetching the project authors.
  1. 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
  2. 13 May, 2005 1 commit
  3. 09 May, 2005 1 commit
  4. 06 May, 2005 1 commit
  5. 31 Mar, 2005 1 commit
  6. 16 Mar, 2005 1 commit
    • acurtis@pcgem.rdg.cyberkinetica.com's avatar
      Bug#8670 · 1a64fe06
      acurtis@pcgem.rdg.cyberkinetica.com authored
        Rework to resolve ambigious grammer: conflict in join expression
        handling of parentheses for nested joins and derived tables.
        Tests included of failing statements
      Optimize item construction for AND/OR logical expressions
      1a64fe06
  7. 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
  8. 17 Feb, 2005 2 commits
  9. 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
  10. 18 Jan, 2005 1 commit
  11. 04 Jan, 2005 1 commit
    • monty@mysql.com's avatar
      After merge fixes · 7cf8285b
      monty@mysql.com authored
      Add support for warnings for prepare of prepared statements
      Fixed test to work with --ps-protocol
      Fixed some test results
      7cf8285b
  12. 03 Jan, 2005 1 commit
  13. 28 Nov, 2004 1 commit
  14. 26 Nov, 2004 1 commit
  15. 16 Nov, 2004 1 commit
  16. 10 Nov, 2004 1 commit
    • igor@rurik.mysql.com's avatar
      select.result, select.test: · 597781c1
      igor@rurik.mysql.com authored
        Added test cases for bug #6474.
      sql_select.cc:
        Fixed bug #6474. A wrong result was returned when a query
        contained the same equality of the form field=const on
        different AND levels.
      597781c1
  17. 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
  18. 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
  19. 02 Oct, 2004 1 commit
    • monty@mishka.local's avatar
      More fixes for strict mode: · be4ca46f
      monty@mishka.local authored
      More tests.
      Better error messages.
      Fixed bug when checking if we updated all needed columns for INSERT.
      Give an error if we encounter a wrong float value during parsing.
      Don't print DEFAULT for columns without a default value in SHOW CREATE/SHOW FIELDS.
      Fixed UPDATE IGNORE when using STRICT mode.
      be4ca46f
  20. 07 Sep, 2004 2 commits
  21. 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
  22. 30 Aug, 2004 1 commit
  23. 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
  24. 22 Jan, 2004 1 commit
  25. 10 Dec, 2003 1 commit
  26. 30 Oct, 2003 1 commit
  27. 16 Sep, 2003 1 commit
  28. 25 Jul, 2003 1 commit
  29. 26 Jun, 2003 1 commit
  30. 13 Mar, 2003 1 commit
  31. 11 Mar, 2003 1 commit
  32. 07 Mar, 2003 1 commit
  33. 05 Jan, 2003 1 commit
  34. 13 Dec, 2002 1 commit
  35. 04 Dec, 2002 1 commit
  36. 15 Oct, 2002 1 commit
  37. 12 Oct, 2002 1 commit
    • pem@mysql.com's avatar
      Task 430: Allowing braces in joins by simply removing them. · 8bd61c3f
      pem@mysql.com authored
      This is a simple fix, allowing a join_table_list in the right reduction of a
      normal_join sequence, instead of just a join_table. This makes things like
      "t1, (t2 left join t3)" work, but it also allows "join" and "cross join" instead
      of ",".
      
      This should fix the bug reported as:
        Subject: ODBC SQL syntax issue 
        From: Ivan Vazharov 
        Date: Mon, 30 Sep 2002 12:02:42 +0200 
      8bd61c3f
  38. 11 Oct, 2002 1 commit