An error occurred fetching the project authors.
  1. 02 May, 2007 1 commit
  2. 25 Apr, 2007 1 commit
  3. 23 Apr, 2007 1 commit
  4. 19 Apr, 2007 1 commit
  5. 18 Apr, 2007 1 commit
  6. 12 Apr, 2007 1 commit
  7. 11 Apr, 2007 1 commit
  8. 05 Apr, 2007 1 commit
  9. 04 Apr, 2007 1 commit
    • mskold/marty@mysql.com/linux.site's avatar
      Bug #26242 UPDATE with subquery and triggers failing with cluster tables · 625a2629
      mskold/marty@mysql.com/linux.site authored
      In certain cases AFTER UPDATE/DELETE triggers on NDB tables that referenced
      subject table didn't see the results of operation which caused invocation
      of those triggers. In other words AFTER trigger invoked as result of update
      (or deletion) of particular row saw version of this row before update (or
      deletion).
      
      The problem occured because NDB handler in those cases postponed actual
      update/delete operations to be able to perform them later as one batch.
      
      This fix solves the problem by disabling this optimization for particular
      operation if subject table has AFTER trigger for this operation defined.
      To achieve this we introduce two new flags for handler::extra() method:
      HA_EXTRA_DELETE_CANNOT_BATCH and HA_EXTRA_UPDATE_CANNOT_BATCH.
      These are called if there exists AFTER DELETE/UPDATE triggers during a
      statement that potentially can generate calls to delete_row()/update_row().
      This includes multi_delete/multi_update statements as well as insert statements
      that do delete/update as part of an ON DUPLICATE statement.
      625a2629
  10. 03 Apr, 2007 1 commit
  11. 02 Apr, 2007 1 commit
  12. 26 Mar, 2007 2 commits
  13. 24 Mar, 2007 1 commit
  14. 23 Mar, 2007 1 commit
    • aelkin/elkin@andrepl.(none)'s avatar
      Bug #27395 OPTION_STATUS_NO_TRANS_UPDATE is not preserved at the end of SF() · 2afa90b5
      aelkin/elkin@andrepl.(none) authored
      thd->options' OPTION_STATUS_NO_TRANS_UPDATE bit was not restored at the end of SF() invocation, where
      SF() modified non-ta table.
      As the result of this artifact it was not possible to detect whether there were any side-effects when
      top-level query ends. 
      If the top level query table was not modified and the bit is lost there would be no binlogging.
      
      Fixed with preserving the bit inside of thd->no_trans_update struct. The struct agregates two bool flags
      telling whether the current query and the current transaction modified any non-ta table.
      The flags stmt, all are dropped at the end of the query and the transaction.
      2afa90b5
  15. 22 Mar, 2007 2 commits
  16. 21 Mar, 2007 1 commit
  17. 28 Feb, 2007 1 commit
  18. 21 Feb, 2007 1 commit
  19. 14 Feb, 2007 1 commit
  20. 09 Feb, 2007 1 commit
  21. 07 Feb, 2007 1 commit
  22. 06 Feb, 2007 1 commit
  23. 01 Feb, 2007 1 commit
  24. 31 Jan, 2007 1 commit
  25. 24 Jan, 2007 1 commit
  26. 23 Jan, 2007 2 commits
  27. 22 Jan, 2007 1 commit
  28. 17 Jan, 2007 2 commits
  29. 08 Jan, 2007 1 commit
  30. 23 Dec, 2006 1 commit
  31. 15 Dec, 2006 1 commit
  32. 14 Dec, 2006 2 commits
  33. 30 Nov, 2006 3 commits