An error occurred fetching the project authors.
  1. 30 Sep, 2005 1 commit
    • serg@serg.mylan's avatar
      Bug#11238 · bef3c587
      serg@serg.mylan authored
      "SELECT ... FOR UPDATE executed as consistent read inside LOCK TABLES"
      Do not discard lock_type information as handler::start_stmt() may require knowledge.
      (fixed by Antony)
      bef3c587
  2. 29 Sep, 2005 2 commits
  3. 28 Sep, 2005 1 commit
  4. 23 Sep, 2005 2 commits
  5. 19 Sep, 2005 1 commit
  6. 13 Sep, 2005 1 commit
    • monty@mishka.mysql.fi's avatar
      Added option --valgrind-mysqltest to mysql-test-run · f348f62c
      monty@mishka.mysql.fi authored
      Added flag to Field::store(longlong) to specify if value is unsigned.
      This fixes bug #12750: Incorrect storage of 9999999999999999999 in DECIMAL(19, 0)
      Fixed warning from valgrind in CREATE ... SELECT
      Fixed double free of mysql.options if reconnect failed
      f348f62c
  7. 12 Sep, 2005 1 commit
  8. 06 Sep, 2005 1 commit
  9. 31 Aug, 2005 1 commit
  10. 29 Aug, 2005 1 commit
  11. 23 Aug, 2005 1 commit
    • timour@mysql.com's avatar
      WL#2486 - natural and using join according to SQL:2003 · e0403003
      timour@mysql.com authored
      * Provide backwards compatibility extension to name resolution of
        coalesced columns. The patch allows such columns to be qualified
        with a table (and db) name, as it is in 4.1.
        Based on a patch from Monty.
      
      * Adjusted tests accordingly to test both backwards compatible name
        resolution of qualified columns, and ANSI-style resolution of
        non-qualified columns.
        For this, each affected test has two versions - one with qualified
        columns, and one without. 
      e0403003
  12. 19 Aug, 2005 1 commit
  13. 17 Aug, 2005 1 commit
  14. 12 Aug, 2005 1 commit
    • timour@mysql.com's avatar
      Implementation of WL#2486 - · a247282a
      timour@mysql.com authored
      "Process NATURAL and USING joins according to SQL:2003".
      
      * Some of the main problems fixed by the patch:
        - in "select *" queries the * expanded correctly according to
          ANSI for arbitrary natural/using joins
        - natural/using joins are correctly transformed into JOIN ... ON
          for any number/nesting of the joins.
        - column references are correctly resolved against natural joins
          of any nesting and combined with arbitrary other joins.
      
      * This patch also contains a fix for name resolution of items
        inside the ON condition of JOIN ... ON - in this case items must
        be resolved only against the JOIN operands. To support such
        'local' name resolution, the patch introduces a stack of
        name resolution contexts used at parse time.
      
      NOTICE:
      - This patch is not complete in the sense that
        - there are 2 test cases that still do not pass -
          one in join.test, one in select.test. Both are marked
          with a comment "TODO: WL#2486".
        - it does not include a new test specific for the task
      a247282a
  15. 09 Aug, 2005 1 commit
    • evgen@moonbone.local's avatar
      Fix bug #12340 Wrong comparison in ha_innobase::cmp_ref() · 2a025ffb
      evgen@moonbone.local authored
      When PRIMARY KEY is present ha_innobase::cmp_ref() uses it to compare refs.
      After comparing part of key it moves pointers to compare next part.
      For varchar parts pointers were moved only by length of parts, not including
      bytes containig part length itself. This results in wrong comparision and
      wrong number of deleted records.
      2a025ffb
  16. 28 Jul, 2005 1 commit
  17. 14 Jul, 2005 1 commit
  18. 20 Jun, 2005 1 commit
  19. 07 Jun, 2005 2 commits
  20. 06 Jun, 2005 2 commits
  21. 03 Jun, 2005 1 commit
    • monty@mysql.com's avatar
      Move USE_PRAGMA_IMPLEMENTATION to proper place · 29fd1f2f
      monty@mysql.com authored
      Ensure that 'null_value' is not accessed before val() is called in FIELD() functions
      Fixed initialization of key maps. This fixes some problems with keys when you have more than 64 keys
      Fixed that ROLLUP don't always create a temporary table. This fix ensures that func_gconcat.test results are now predictable
      29fd1f2f
  22. 27 May, 2005 1 commit
  23. 07 May, 2005 2 commits
  24. 06 May, 2005 1 commit
  25. 14 Apr, 2005 1 commit
  26. 12 Apr, 2005 1 commit
  27. 04 Apr, 2005 1 commit
  28. 30 Mar, 2005 1 commit
  29. 16 Mar, 2005 2 commits
  30. 11 Mar, 2005 1 commit
  31. 02 Mar, 2005 1 commit
  32. 24 Feb, 2005 1 commit
  33. 23 Feb, 2005 1 commit
  34. 21 Feb, 2005 1 commit