1. 11 May, 2006 1 commit
  2. 06 May, 2006 1 commit
  3. 04 May, 2006 1 commit
  4. 25 Apr, 2006 2 commits
  5. 11 Apr, 2006 3 commits
  6. 10 Apr, 2006 3 commits
  7. 08 Apr, 2006 1 commit
  8. 07 Apr, 2006 1 commit
  9. 06 Apr, 2006 1 commit
  10. 03 Apr, 2006 1 commit
  11. 01 Apr, 2006 1 commit
  12. 02 Mar, 2006 2 commits
  13. 01 Mar, 2006 4 commits
  14. 20 Feb, 2006 1 commit
  15. 12 Feb, 2006 1 commit
  16. 28 Jan, 2006 1 commit
  17. 23 Jan, 2006 2 commits
    • evgen@moonbone.local's avatar
      Fixed bug #16510: Updating field named like '*name' caused server crash. · b1967ad7
      evgen@moonbone.local authored
      When setup_fields() function finds field named '*' it expands it to the list
      of all table fields. It does so by checking that the first char of
      field_name is '*', but it doesn't checks that the '* is the only char.
      Due to this, when updating table with a field named like '*name', such field
      is wrongly treated as '*' and expanded. This leads to making list of fields
      to update being longer than list of the new values. Later, the fill_record() 
      function crashes by dereferencing null when there is left fields to update,
      but no more values.
      
      Added check in the setup_fields() function which ensures that the field
      expanding will be done only when '*' is the only char in the field name.
      b1967ad7
    • ingo@mysql.com's avatar
      BUG#5390 - problems with merge tables · 87f9c10d
      ingo@mysql.com authored
      After-fix optimizations proposed and finally
      implemented by Monty.
      87f9c10d
  18. 17 Jan, 2006 1 commit
  19. 16 Jan, 2006 2 commits
  20. 13 Jan, 2006 1 commit
  21. 12 Jan, 2006 1 commit
  22. 06 Jan, 2006 1 commit
  23. 27 Dec, 2005 1 commit
  24. 18 Dec, 2005 1 commit
  25. 13 Dec, 2005 1 commit
  26. 06 Dec, 2005 2 commits
  27. 04 Dec, 2005 1 commit
  28. 29 Nov, 2005 1 commit
    • ingo@mysql.com's avatar
      BUG#5390 - problems with merge tables · 76861ac6
      ingo@mysql.com authored
      Problem #1: INSERT...SELECT
      INSERT ... SELECT with the same table on both sides (hidden
      below a MERGE table) does now work by buffering the select result.
      The duplicate detection works now after open_and_lock_tables() 
      on the locks.
      I did not find a test case that failed without the change in
      sql_update.cc. I made the change anyway as it should in theory
      fix a possible MERGE table problem with multi-table update.
      76861ac6